メインコンテンツへスキップ

Desktop (WG)

These documents own Desktop-specific contracts: native presentation, the renderer bridge, browser pages and host services. Agent-related pages describe the Desktop binding of the agent RFC.

For the abstract contract:

  • Agent system RFC — protocol, locked tools, sessions, capability surface, sandbox placement.
  • Grida bindings — how the locked tools, the filesystem backends, and the built-in subagents land in Grida.
  • Grida Gateway (GG) — the shipped no-key AI path: scoped-token federation → metered first-party gateway → org-credit spend. BYOK still bypasses it.

For the user-facing app and the security boundary:

Pages​

The built-in browser defines standalone page ownership, profile isolation, document lifetime and live workbench composition.

PageCovers
Process modelElectron main / native agent host / socketless ServicesSidecar / renderer — what each owns, main-owned loopback, and provider frames.
Renderer bridgeURL-loaded renderer doctrine — loadURL("grida.co/desktop/*"), path-scoped window.grida, DesktopBridgeGate.
Resource loadingHow the renderer gets host-owned resource bytes — buffered (data:) vs streamed (privileged grida-workspace: scheme), Range/seeking, proxy-not-new-authority.
Agent securityDesktop binding of GRIDA-SEC-004: bridge path scope, HTTP perimeter, sandbox, and secrets discipline.
Desktop agent authorityThe Desktop delta for contained host services, native host networking, per-principal raw execution, and permission modes above confinement.
Agent storage layoutWhich process keeps which files: native chat state, sidecar registries, credentials, preferences, and the earlier chat store.

Processes​

Desktop chat runs in the native agent host, which Electron main supervises over private stdio. The retained sidecar is one composed server — the daemon frame with the media routes — that owns media generation, files, recents, workspaces, and secrets, and runs no chat. The renderer drives chat through main's native chat bridge. See Process model.