Vault agent tools — retired; how agents reach your notes now
The per-session Vault (KMS) MCP tools — kms_search, kms_read and the rest — were retired on 2026-09-19, and the "Expose Vault to spawned agents" switch that turned them on has been removed from Settings. Agents still work with your notes; they just reach them a different way (below).
On this page
What it is
The Vault is Omniscio's built-in Markdown notes editor over a folder you choose (see kms.md). It used to give every Claude session Omniscio started an extra MCP server with read-only kms_* tools. That server is no longer added to any session, so the switch that controlled it has nothing left to switch.
Where to find it
Nowhere — the row is gone from Settings → Features → Vault. The stored setting behind it is kept so an existing configuration still loads, but no screen shows it and nothing reads it.
How it behaves
- Sessions started from the Vault. The Vault toolbar's Ask AI menu (Summarize this note, Find related notes, Ask a question...) starts a session inside your vault folder. It reads and edits the
.mdfiles directly with its normal file tools. - Omniscio's own Vault routes. Agents and skills use the app's
/kms/*routes to search, read, create and update notes. A spawned session calls them with its OWN token ($AMC_CLI_TOKEN), which is enough for reads and writes; the install-wide token still works, but a write through it may not name a session. Deleting a note waits for your approval in the inbox unless you have turned off Require approval: Vault deletes in Settings. - Notes pinned as context. Pin up to 5 notes to a hub, and every new session in that hub starts with them.
Related
- kms.md — the parent Markdown vault feature
- kms-summaries.md — the AI summary marker codec the tools'
summaryfield surfaces - mempalace-memory.md — the related memory integration; consult its page for its current agent path
Last verified 2026-11-16