Aller au contenu principal

AI (WG)

Three siblings live here:

  • agent/ — the implementation-agnostic agent system RFC. RFC 2119 normative tone. No product-specific references. Plays a role similar to ACP or LSP: the contract a conforming implementation MUST honor.
  • grida/ — Grida-specific bindings of the RFC. The canvas-tool catalog, the image-generation surface, the built-in subagents (titler / compactor / planner), and how Grida's host wires the locked-tool set.
  • grida/architecture.md — Grida's implementation blueprint. Names the orchestrator god class (AgentHost), the package map, the host landings, the sequencing, and the anti-goals. Read this first if you're implementing.

Reading order​

If you're trying to understand the system end-to-end:

  1. Start at agent/index.md for vocabulary and the cross-cutting invariants.
  2. Read agent/foundations.md for the bedrock (AI SDK v6 chunk shape, the locked-tool set summary, the watchdog, the directory-rooted execution model).
  3. Skim the locked-tool spec in agent/tools.md and the storage shape in agent/persistency.md.
  4. Pick the surface that matches your work — sessions, subagents, skills, MCP, environments — from the agent/ sidebar.
  5. Cross over to grida/ for the bindings, the Grida-canvas tool surface, and the image-generation tools.

If you're trying to build Grida's implementation:

  1. Start at grida/architecture.md for the blueprint.
  2. Then steps 2–4 above.
  3. Then ../desktop/ for the V1 host landing.

Scope​

This WG focuses on the agent protocol and Grida's bindings. Provider auth and credentials are out of scope (host territory). The hosted billing / model-seam architecture lives in ../platform/.