Agent security
Desktop binding of GRIDA-SEC-004 and GRIDA-SEC-008 for ServicesSidecar, the renderer bridge, HTTP perimeter, sandbox, native provider OAuth, and secrets discipline.
Native shell, browser pages, renderer integration, and Desktop host services.
Voir toutes les étiquettesDesktop binding of GRIDA-SEC-004 and GRIDA-SEC-008 for ServicesSidecar, the renderer bridge, HTTP perimeter, sandbox, native provider OAuth, and secrets discipline.
Which Desktop process keeps which files — the native agent host's chat state and the retained sidecar's registries and credentials.
Browse and search the web in Grida Desktop, find recently visited pages, and manage shared history and website data.
Ownership, navigation, website interaction and storage contracts for browser pages inside Grida Desktop.
Architecture and behavior contracts for Grida Desktop's native shell, browser, renderer and hosted services.
The Desktop delta for host containment, native host networking, and confined raw agent execution.
Why Grida Desktop runs the native agent host and a retained media sidecar beside Electron main, what each owns, and where the boundaries sit.
Why Grida Desktop URL-loads grida.co/desktop/* instead of bundling editor source — the "one editor codebase, two hosts" doctrine and the path-scoped window.grida bridge.
How the desktop renderer obtains host-owned resource bytes (workspace files — text, images, video) — the buffered-vs-streamed transport model, the privileged media scheme, and why the host proxies rather than handing the renderer or main process its own file authority.