KMS Session Seeds (multi-note briefing + project context notes)
Two ways to pre-load KMS notes into a Claude session so the AI starts with real context rather than a blank slate: a multi-note briefing that assembles two to five selected notes into one opening prompt, and project context notes attached to a project so its sessions begin already briefed.
On this page
What it is
Two ways to pre-load KMS notes into Claude sessions so the AI starts with real context instead of a blank slate. Both are gated by the parent KMS toggle (nothariEnabled).
Where to find it
The briefing starts from the KMS file tree — select two to five notes, right-click, and choose Start briefing; the session it opens lands in the KMS Sessions tab. Project context notes are pinned from that same file tree, with Pin to <project name> (see How to pin), and managed from the project itself: open the project's menu, choose Edit, then More options, where the Pinned Vault notes list opens, reorders and unpins them. Agents use the CLI routes under Managing pinned notes or the KMS_PROJECT_CONTEXT_* IPC channels.
How it behaves
Multi-note briefing
Select 2-5 notes in the file tree (Ctrl+Click / Shift+Click), right-click, and choose Start briefing (N notes). The app reads every selected note's full body via KMS_NOTE_READ, assembles them via buildBriefingPrompt (each note titled and fenced, per-note cap 20 KB, total cap 80 KB), and opens the shared Start session dialog with the assembled notes as its item details. Type an optional question in Message, pick a repo or model if you like, and press Start: the session gets your question, a short note saying which notes it was briefed on, then the notes themselves. If some notes could not be read, the briefing uses the ones that could and tells you once it starts; fewer than two readable notes start nothing. The session opens in the KMS Sessions tab.
- Where it lives: file tree context menu (bulk mode, 2-5 selection), the
useNoteBriefinghook, andopenVaultBriefingStartSession(vault-start-session.ts), which opens the shared Start session dialog. - Limits: 2-5 notes (below or above that range the menu row is hidden), 20 KB per note body, 80 KB total. Truncated notes get a hint to open the note in the Vault for the full version — never a tool name (Vault agent tools).
- No Vault tools needed: the briefing prompt carries the full note bodies inline; the
kms_read/kms_searchMCP tools it was written around were retired on 2026-09-19.
Project context notes
Designate 1-5 notes as standing context for a real (non-virtual) project. Every new session spawned in that project automatically receives the pinned notes' current bodies via the session-context provider system, no manual selection needed.
The context is capped, so a long note arrives cut. Each pinned note is cut at 25 KB, and the pinned notes together stop at 100 KB — notes past that point are not included at all. A cut note carries a line saying it was truncated and that the full version stays in the Vault and is not directly reachable from that session. The briefing cap above (20 KB per note, 80 KB total) is a different limit on a different feature, so a note can fit one and be cut by the other.
How to pin
Right-click a single note in the file tree. With one real project you get a direct Pin to <project name> row; with several you get a single Pin to project entry whose submenu flyout lists every real project — so the menu stays tidy no matter how many projects you have. Picking a project adds the note to that project's context list. Pinning a note the project already has leaves that one pin in place and reports success rather than an error, so a double-click or a retried pin changes nothing. If the project already has 5 context notes, a NEW note is rejected with a cap-exceeded error.
How it works
A content-matched SessionContextProvider registered in CONTENT_PROVIDERS checks matches(folderPath) at session spawn time. If the project has pinned context notes, build() reads their current bodies from the DB (fresh, not cached) and assembles them via buildProjectContextPrompt. The result is injected as a system-context block alongside other providers.
- Living context: note bodies are read at spawn time, so an updated note automatically appears in the next session. No re-pinning needed.
- No kms_read hint: unlike the briefing prompt, the project context prompt does not hint at
kms_read— a retired tool name now (Vault agent tools), and real-project sessions never carry Vault tools.
Managing pinned notes
- CLI:
GET /kms/project-context?project=<folder path>(list — the query field isproject, and any other spelling gets400),POST /kms/project-context(add — approval-gated: it queues a card and pins only once the person approves),DELETE /kms/project-context/:id(remove). - IPC:
KMS_PROJECT_CONTEXT_LIST,KMS_PROJECT_CONTEXT_ADD,KMS_PROJECT_CONTEXT_REMOVE,KMS_PROJECT_CONTEXT_REORDER. - Push: mutations emit
KMS_PROJECT_CONTEXT_CHANGEDso open panels reconcile. - DB table:
nothari_project_context_notes(soft-delete,is_deleted = 0filter on all queries).
Settings
No new settings. Both features are gated by the existing Vault toggle (nothariEnabled, set by installing The Vault from Marketplace → Inbuilt). The vault root (nothariVaultRootPath) must be configured for briefing to work.
Related
Asking the vault a question directly, rather than briefing a session with notes you picked by hand, is described on the KMS — AI, windows and sharing page under its one-click note-seeded chat. The agent tools a seeded session can use are on KMS agent tools.
Last verified 2026-09-23