Local MCP interface
Compatible MCP clients can list projects, search memory, and build a context package through three read-only tools. The bridge runs on loopback, reads its private configuration from the desktop data directory, and checks desktop authorization.
Chrome capture
The Chrome extension adds a context-menu action for selected text and a popup for a quick note. It sends the capture to the paired local desktop bridge, which writes it into the chosen project on the same authorized computer.
Import and file workflows
The desktop accepts JSON conversations and selected text files. It records imports locally, skips duplicate conversations, and preserves revisions when an imported file changes at the same path. It does not poll folders or connect to AI provider accounts.
No remote memory endpoint
There is no public endpoint for reading project contents. Account and billing APIs manage identity and entitlement; local MCP and extension capture are separate, authenticated local connections.