Quick start

This guide uses the global store, which is selected by default. It is the shortest path from installation to a searchable memory.

Initialize a store

sbuf init

Inspect the store

Use root and status to confirm which store is selected:

sbuf root
sbuf status

Add --json to status for machine-readable output.

Create and manage a memory

add opens a Markdown record in $VISUAL or $EDITOR:

sbuf add --title "Release constraint" --kind fact
sbuf list

Save one durable claim and include its source. list shows active records. The CLI reference covers editing and lifecycle commands.

Search your memory

Search active memory with:

sbuf search release

Use context when another program needs a machine-readable selection within a token budget:

sbuf context release --budget 400

Search results cite the matching record. Context output preserves those citations while selecting only what fits the requested budget.

Use a project store

When knowledge belongs to one repository, initialize its store from that repository. --project searches that store together with applicable global memory:

sbuf --project init
sbuf --project status

Use --local when you need strict repository isolation:

sbuf --local search "repository-only note"

The local view never opens the global store. Both views use the same project identity, which remains stable if the repository directory is renamed.

See The memory loop for what belongs in each store. Backup and recovery explains how to keep project memory private or share a curated store with a repository.