Grida bindings
These docs describe how Grida implements and extends the implementation-agnostic agent RFC. The RFC specifies shapes (locked tool set, capability surface, session schema, ACP wire) without dictating product-specific behavior; this layer binds those shapes to Grida's actual surfaces — the canvas, the image-generation provider seam, and the host-level fundamentals as Grida ships them.
Pages
| Page | Covers |
|---|---|
| Architecture (start here for implementation) | Grida's master implementation blueprint. Orchestrator god class (AgentHost), package map, host landings, sequencing, anti-goals. |
| Fundamental Tools (Grida binding) | How the locked-tool RFC (../agent/tools.md) lands in Grida — virtual-fs adapter, in-canvas bash, host wiring. |
| Canvas Tools | The canvas-only tool surface: scene-graph search and selection, specialized inserts, canvas exec / lint / format, resource lookup. Requires an active editor instance. |
| Image Tools | Image-generation tools: text-to-image and image-to-image, provider-agnostic abstraction, credit-aware operations, canvas-image-node integration. |
| Built-in subagents | Grida's specialized subagents (titler today; compactor + planner future). Concrete tier / model / sentinel / cost-discipline bindings of the RFC subagent pattern. |
See also
- Agent RFC — the protocol these bindings ride on.