KMS Vault Overview (searchable inventory table of every note)
A read-only table showing every note in the active vault on one screen — title, tags, summary state and text, estimated token count, size and last-modified — sortable and searchable. It is the bird's-eye complement to the note editor, for auditing a large vault or judging what a note would cost to load.
On this page
What it is
The Vault Overview is a read-only, searchable, sortable table that shows every visible note in the active vault on one screen: title, tags, AI summary state and text (when a summary marker is already present), estimated token count, byte size, and last-modified timestamp. It is the "bird's-eye" complement to the note-by-note editor — useful for auditing a large vault, finding notes by tag or summary content, and getting a rough sense of how much context each note would consume in an agent session.
The Overview never reads full note bodies and never generates summaries. Summary text is decoded from the first 800 characters of each note (where the <!-- kms:summary … --> marker lives), and size + token estimates come from the body_bytes column — so loading the table costs I/O proportional to row count, not total vault bytes. On a 10 000-note vault the query is still fast.
Gating. The panel is gated by the nothariOverviewEnabled setting (default on). With the Vault itself off (nothariEnabled: false) the panel never loads.
Where to find it
Inside the Vault panel, as the Vault Overview view of the active vault. It is a read-only table — there is no editing here — and it can be turned off in Settings if you would rather not see it.
How it behaves
How to use it
- Open the Overview. In the Vault toolbar, click the Vault Overview button (a list/table icon). The panel is also reachable from the command palette (
Ctrl+Shift+P→ "Vault Overview"). You can also pressCtrl+Shift+O. - Search. The filter input at the top narrows rows by title, tags, or summary text as you type.
- Sort. Three column headers are clickable: Title, Tokens / Size and Updated. A second click on the same header reverses the order. Summary and Tags are labels only — they do not sort.
- Read the summary chip. Each row shows a small chip for the note's summary state: Up to date (green), Stale (amber), Locked (grey), or no chip when the note has no summary marker. The summary text itself appears in the row when the note has a marker. See kms-summaries.md for the full lifecycle.
- Open a note. Clicking any row opens that note in the Vault editor, the same as clicking it in the file tree.
- Turn it off. Settings → Features → Vault Overview → switch it off (
nothariOverviewEnabled).
How it stays current
The panel is not a snapshot. It re-reads the vault when its contents change, and until you close it you do not have to come back to it to see a fresh value.
- One note edited → one row patched. A note save pushes the changed row itself (a body-less snapshot). The Overview matches it to the row with the same note id and updates that row's title, last-modified stamp, byte size and token estimate in place, then re-sorts. Nothing else in the table is re-read.
- A note added, removed, renamed or moved → the table re-reads. Those pushes do not carry enough to place or drop a row, so the panel re-reads the vault, at most once every two seconds — a burst of autosaves still costs one read.
- Another vault's push is ignored. A push names its vault; a note change in a vault you are not looking at changes nothing on screen.
- A summary state change → the table re-reads. A note's summary text lives inside its body, so the summary push (which carries only the state) triggers the same spaced-out re-read. Tags likewise come from the re-read rather than the push.
- While the panel is hidden it does nothing. Under KMS keep-warm the panel stays mounted when you navigate away, and a hidden panel ignores pushes entirely; it catches up with one read the moment it is shown again. This is
kms-keep-warm-contractrule 7, the same rule that governs the file tree.
A whole-vault read therefore happens only when the panel opens, when a note appears, goes away or changes path, and when a summary state moves — never on a plain save, never on another vault's activity, and never while the panel is hidden.
Known limitations
- Token count is an estimate, not an exact count.
tokenEstimateusesceil(body_bytes / 4)— a bytes-per-token heuristic, not a model tokenizer. For notes that are primarily ASCII prose the approximation is close; notes with many multi-byte characters (CJK, emoji, code) will have a higher real token count than the estimate shows. - Summaries shown only when already generated. The Overview reads and displays whatever summary marker is already in a note — it never triggers summary generation. A note that has never been summarised shows
summary.state: 'none'andsummary.text: null. Neither the in-editor chip nor the opt-in auto-regen worker can give such a note its first summary: the chip renders nothing at all in thenonestate, and the worker only picks up notes already marked stale or budget-capped. The first summary comes from the bulk summary seeding card in Settings → Features → Vault, which walks every un-summarized note (see kms-summaries.md). - The agent route is one vault per call.
GET /kms/inventoryanswers for a single vault (the onevaultIdnames, else the configured vault), with no cursor, so a multi-vault install needs one call per vault.
Related
- kms.md — the parent KMS vault editor (vault setup, the
nothariEnabledmaster toggle, file structure) - kms-agent-tools.md — how agents reach your notes now that the per-session
kms_*MCP tools (kms_inventoryamong them) are retired - kms-summaries.md — the AI summary marker lifecycle that the Overview's summary column and the
summaryfield surface
Last verified 2026-11-17