Developers

Egg is a desktop browser with a built-in agent platform. These reference docs describe how it’s built and the surfaces a developer can integrate with.

Egg runs as two coordinating processes on the user’s machine: a Tauri-based browser shell that owns tabs, chrome, and the user-facing UI, and a long-running Rust daemon (egg-daemon) that hosts the agent harness, polls feeds, runs scheduled monitors, drives hidden engine instances for collection work, and serves a local HTTP API. The split is deliberate: it lets the agent keep working when no browser window is open, and keeps long-running services out of a process that exits when the UI closes.

The web engine is the platform’s native one. WebView2 (Chromium + Blink) on Windows, WKWebView (WebKit) on macOS. No embedded second engine, no pinned browser binary. Page-side compatibility (Service Workers, WebAssembly, PWAs, Chrome extensions) follows what each platform’s engine supports.

The agent platform is local-first by design. The default model is a local Ollama install on the user’s hardware; cloud LLM providers are an opt-in capability burst, not the default routing. The Egg app and gateway send no telemetry of their own, and engine-level telemetry is disabled wherever the underlying WebView2 or WKWebView API allows it. Multi-device sync rides through a relay that only ever sees opaque ciphertext, with end-to-end keys derived per pairing and held in the OS keychain. A URL-pattern firewall gates what an agent can do when it reaches into the browser, with conservative defaults on financial, healthcare, and email categories.

The first-class apps that ship inside Egg (Feed, People, Studio, Explore, Agent, and others) are built on a platform called Egglets. An Egglet is a sandboxed app that declares its runtime surface (LLM router, Gateway services, network, cross-Egglet messaging, refs, credentials, headless fetch) in a manifest, and the host enforces that contract at runtime. Every backing the Egglet is allowed to touch is in the manifest, and the Settings panel surfaces what each Egglet has actually used so the user can see the real footprint, not just the declared one.