---
title: Update Vault (/update-vault skill)
---

# Update Vault

## What it is

A built-in skill that scans your Omniscio sessions and logs what they did into your KMS vault (The Vault). It extracts PRs shipped, bugs found and fixed, features built, test results, UX improvements, costs, and blockers; then updates the matching vault note for each session's feature or project. Nothing is lost between sessions.

Two modes:

- **This session** (default when you invoke it manually): extracts findings from the current session and updates the vault before you archive it.
- **Batch scan** (when you say "scan all", "daily scan", "catch up"): scans every session from the last 24 hours across all projects and updates every matching vault note in one pass. Configurable lookback (24h / 72h / 1 week).

The skill is read-only for sessions; it never modifies, archives, or deletes them.

## Where to find it

There is no panel, menu, or settings page of its own — it is a built-in skill you invoke by typing `/update-vault` in a session. The one thing it needs first is a vault: set one up in Settings > The Vault (KMS) with at least one vault root path.

## How it behaves

### Prerequisites

You need a vault configured in Settings > The Vault (KMS) with at least one vault root path set. The skill discovers the vault location and structure automatically via `GET /kms/vaults` and `GET /kms/notes`; nothing is hardcoded.

### How to use it

Type `/update-vault` in a session. Omniscio will ask which mode you want (or default to batch if invoked by a scheduled job).

**This-session mode** works from the conversation context you already have. The skill matches the session to a vault note (by title, tags, or content), updates that note with findings, and updates the dashboard if one exists.

**Batch mode** calls the Omniscio CLI API to list sessions (`/sessions?limit=200&includeArchived=true&startedAfter=24h`), reads transcripts via `/session/{id}/markdown`, extracts findings from each, and updates every matching vault note. It dispatches 3-5 subagents grouped by topic area for speed.

#### What it updates

For each session it touches:

- **Shipped table** -- new PRs (checked for duplicates by PR number)
- **Bugs Found** -- new bugs with descriptions and fix status
- **Session Log** -- a dated row per session summarizing what happened
- **Bug Log** -- the cross-feature bug index gets any new bugs too (if one exists)
- **Dashboard** -- feature status, bug counts, note counts, last-scan timestamp (if one exists)

Sessions that don't match an existing tracker note get a new note, grouped by topic (not by raw project name).

#### Vault discovery

The skill adapts to any vault structure:

1. `GET /kms/vaults` finds the vault path and ID
2. `GET /kms/notes?vaultId=` maps every existing note (path, title, tags)
3. Sessions are matched to notes by comparing session metadata against note titles, tags, and folder paths
4. New notes are created via `POST /kms/notes` in the appropriate folder (tracker folder, projects folder, or vault root)

No folder names, note numbering, or section headings are assumed. The skill reads what's there and works with it.

#### Onboarding

Historically, a first-run onboarding card introduced the vault skill after the daily-briefing mission launched: _"Your agents' work adds up fast. /update-vault is how you stay on top of it."_ (That onboarding cascade has since been deleted — arch-complexity F003; the skill itself is unchanged.)

## For agents

### How it works

The skill is defined in [.claude/skills/update-vault/SKILL.md](../../.claude/skills/update-vault/SKILL.md); a detailed instruction file that Claude Code loads when you invoke `/update-vault`. It is pure instructions (no compiled code); Claude follows the steps using the Omniscio CLI API and the Read/Write/Edit tools to update vault markdown files directly.

(Historical: the onboarding cascade step that introduced this skill was authored as a JSON `theory` step and rendered by a `CascadeTheoryCard` component — that cascade onboarding was later deleted, arch-complexity F003. The `/update-vault` skill itself is unaffected.)

## Related

- [kms.md](kms.md) -- the KMS/Vault feature itself
- [first-time-setup.md](first-time-setup.md) -- the onboarding wizard and cascade system
- [amc-session-awareness.md](amc-session-awareness.md) -- how sessions know about Omniscio's CLI API