Vault Config

Add/update ('set') or remove a vault in the semantic index's vault_index.vaults config. Writes config.local.yaml (the user-override layer); changes apply on the next vault build (the 5-min cron or a manual vault_index build) — no restart. Removing a vault deletes only its config entry; its already-indexed chunks stay searchable until an explicit prune.

MCP name: vault_config

Category: context

:warning: Requires consent

Mutates state (retry policy: manual)

Parameters

Name	Type	Required	Description
action	str	No	'set' (add/update a vault) or 'remove'
exclude	list	No	Gitignore-style exclude globs.
id	str	Yes	Stable vault id (no '/' or '\'; it namespaces chunk ids). The default vault's id is 'vault'.
include	list	No	Gitignore-style include globs (default ['*/.md']).
path	str	No	Absolute path to the vault root directory (required for 'set').

Details

Editable surface for the vault semantic index's roots. Pairs with vault_index (build/status) and vault_search (query). The dashboard Settings › Embeddings sub-view calls this when a vault row is edited. Persists to config.local.yaml (comments there are not preserved — it's the machine-managed override layer). An edit takes effect on the next build; run vault_index action=build to reconcile immediately. Removing a vault leaves its chunks orphaned-but-searchable until a future prune.