본문으로 건너뛰기

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.

The Rust/Electron tool-host contract defines shared Grida capabilities exposed directly and through MCP, including live editor ownership and headless execution. The pages below also retain current implementation evidence and earlier domain-tool proposals.

Pages​

PageCovers
Architecture (start here for implementation)Grida's implementation blueprint: native agent host, retained media sidecar, Desktop process ownership, capacity providers, anti-goals.
Workspace SurfacesCurrent product model for repository-backed workspaces and visible artifacts: canvas-first policy, agnostic surface tools, host interactivity, user authority, and reopen continuity.
Fundamental Tools (Grida binding)How the locked-tool RFC (../agent/tools.md) lands in Grida — virtual-fs adapter, in-canvas bash, the view_image perception extension (../agent/vision.md), host wiring.
Canvas ToolsThe canvas-only tool surface: scene-graph search and selection, specialized inserts, canvas exec / lint / format, resource lookup. Requires an active editor instance.
Image ToolsImage-generation tools: text-to-image and image-to-image, provider-agnostic abstraction, credit-aware operations, canvas-image-node integration.
Built-in subagentsGrida's specialized internal agents (chat titles and compaction), with their provider and cost bounds.

See also​

  • Agent RFC — the protocol these bindings ride on.