Repository navigation
Integrations
All knowledge integrations are optional. Nothing automatically imports vaults or remote notes. See the integration guide for permission and disclosure boundaries.
| Topic | Canonical guide |
|---|---|
Existing Obsidian directory mounted at /vault
|
Read-only vault setup |
| Deliberate write access and host/sync risks | Write opt-in |
| Private data, attachments and task boundaries | Vault privacy |
| User-local remote Mem setup | Mem configuration |
| Browser/headless authentication | Mem OAuth and SSH callbacks |
| Tool approval versus actual account grants | Permission scopes |
Private ~/.claude/CLAUDE.md
|
Personal instructions |
| Future remote-provider recipes | Recipe acceptance |
A read-only filesystem mount prevents writes but permits reading and possible external disclosure. A read-only prompt does not remove a write-capable OAuth grant. Review real provider/tool scopes, minimize mounted paths and revoke unused grants at the provider.
No personal note IDs, private standing orders, account data or sample credentials are distributed. Live Mem OAuth and the user's actual vault remain distinct acceptance scenarios from synthetic tests.
Next: Security, Architecture. Documentation home.
Procedures live in the reviewed canonical repository guides. Wiki pages provide navigation and do not add runtime capabilities. Security reporting · Roadmap