Agent asks
“Does Daemon send my pages to a cloud memory service?”
Local agent memory · Chrome on macOS
Daemon saves allowed pages to an owner-controlled SQLite file on your Mac, then gives connected agents citation-backed evidence through non-destructive MCP tools.
Quick start
Companion service, Chrome extension, then one non-destructive MCP connection.
# Public source install
git clone https://github.com/AadityasinhJadeja/Daemon-Mode.git
cd Daemon-Mode
./tools/install-local-service-launch-agent.sh
# Browser setup
# Connect Codex · replace codex with claude-code, cursor, or claude-desktop
python3 tools/setup-agent-harness.py --apply codex --scope user
Why agent memory matters
Daemon turns allowed reading into reusable evidence, then brings it back where your agents already work.
Agent asks
“Does Daemon send my pages to a cloud memory service?”
Evidence selected locally
01Grounded response
No. Allowed page data moves from Chrome to the companion service on your Mac. Optional provider-backed prose is separate and explicit.
Allowed pages are saved locally without asking you to tag, file, or summarize them.
Example agent request“Which tools did I compare for this project?”
Local search gives connected agents the page, date, and citation behind what you previously read.
Example agent request“What evidence led me to this approach?”
Agents receive evidence with citations but cannot change the vault. No evidence means no invented answer.
Example agent request“Find the source behind that detail.”
How memory moves
Installation expectations
Chrome captures allowed pages. A background companion service stores and retrieves them. MCP connects the agents you trust.
Questions, answered plainly
The extension only speaks to 127.0.0.1:4317, a service on your Mac. There is no Daemon cloud memory service. If you explicitly enable provider-backed prose, the local service sends your question and selected evidence to the provider you configured.
No. The one-time installer registers a per-user macOS background service. It starts after you log in, returns after a normal reboot once you log in again, and is restarted if the process exits unexpectedly. The dashboard is only a view into that service.
Google Chrome on macOS is the current support promise. Other browsers and operating systems have not been verified end to end.
Banking, healthcare, wallets and payments, mail, private messaging, private AI chats, browser-internal pages, and authentication flows. You can add domains of your own.
In a local SQLite file at ~/Library/Application Support/Daemon Mode/memory.sqlite3 for your macOS user.
No. Capture, protection, local retrieval, and MCP evidence work without one. A key is only needed for optional provider-backed prose.
The extension, local service, MCP server, packaging workflow, and verification tools are public in the GitHub repository.
Need the exact detail? Installation, privacy, support, and security guidance lives in Docs.
Browse Docs