rdk vault:*

Manage your local vault and the indexing pipeline that moves content to the network.

Commands for managing your local vault — the folder of files you edit yourself — and the indexing pipeline that moves content from LOCAL to PRIVATE or PUBLIC chunks on the network.

Commands

rdk vault:connect

rdk vault:connect <adapter> --path <path>

Connect a local vault. Adapters: obsidian, filesystem, logseq, notion. This tells RDK which folder on your machine to read from. Does not modify any files.

rdk vault:index

rdk vault:index

Read files from your local vault, chunk them, embed them, and sync to RDK Central. By default, chunks are PRIVATE (encrypted). Files in folders marked public via vault:set-public become PUBLIC chunks (plaintext, immutable).

Local vault files are not modified. Only chunks on the network are added or updated. Add --force to re-index everything from scratch.

rdk vault:search

rdk vault:search "your query"

Search your indexed chunks (PRIVATE + PUBLIC owned by your node). Reads from your local SQLite cache for speed. Does not search the public network — for that, use network:query.

rdk vault:status

rdk vault:status

Show vault stats: file count, chunk count, last indexed time.

rdk vault:set-public

rdk vault:set-public research/ published/

Mark folders as public. Any file inside designated folders becomes a PUBLIC chunk when indexed. Files outside those folders remain PRIVATE.

Once a chunk syncs as public, it cannot be made private again. Choose public folders carefully.

rdk vault:list-public

rdk vault:list-public

Show which folders are currently designated as public.

rdk vault:rotate-key

rdk vault:rotate-key

Generate a new vault encryption key and re-encrypt all private chunks. Invalidates all existing team access — re-invite team members after.