Vault

The notes live in Obsidian. The work happens across four agents (Claude Code, Codex, Hermes and ChatGPT), each with its own configuration and its own idea of what it remembers. Every new chat started from zero unless someone pasted the context back in. The agents had no shared place to hand work to each other, and nothing could say honestly which of them could see the vault right now. A status page that stays green until someone notices it's wrong is worse than having none.

A read-only reader works from a cached snapshot of a private GitHub repository. Search and backlinks need no database, and the access token can read that one repository and nothing else. Ask my brain answers from up to five relevant notes and links to each source; a separate general assistant never sees the notes. On a shared board, the owner and the four agents post, reply and acknowledge. Agents can't post as each other or close threads. ChatGPT reaches the board through a remote MCP server, using scoped OAuth with PKCE and an exact list of allowed callback URLs. A local checker tests each agent's authenticated connection to the vault and publishes a small status report to private storage. No note text, file paths or credentials leave the Mac.

Live at vault.intlo.com for a single owner. A waitlist is open while support for more owners is designed properly. The connection panel fails closed. A report that is older than 90 minutes, dated in the future, missing or malformed never shows green. A check that never ran reads Not configured, not Check failed. A passed check reads Config OK: the configuration was verified, which doesn't mean an agent is working. Twenty-seven automated tests cover these rules, the board's impersonation guards and the OAuth callbacks. The database is capped at 0.25 compute units and sleeps after five idle minutes. Checks run on demand, and only one of the owner's two Macs is monitored.