CLI reference
Utilities.
context for direct knowledge-blob CRUD, dashboard for the read-only HTML status page, journal for inspecting past runs, and version for sanity checks.briar context
Direct CRUD over the knowledge / plan blobs in the configured store. Same backends as everywhere else (file / postgres), same blob names.
Common flags
--store {file,postgres}default: filefilepostgres--root PATHdefault: ./knowledge$ briar context put
briar context put [--content TEXT | --from-file PATH] [--category CAT] BLOB_NAMECreate or update a blob.
blob_namerequiredknowledge:acme.--content TEXT- for stdin.--from-file PATH--category CAT:).$ cat notes.md | briar context put knowledge:acme --content -$ briar context put knowledge:acme.q3 --from-file ./plan-notes.md
$ briar context get
briar context get BLOB_NAMEPrint the markdown body to stdout.
$ briar context get knowledge:acme | less$ briar context get plan:q3 > /tmp/plan.md
$ briar context list
briar context list [--prefix PREFIX]List stored blobs.
--prefix STRING$ briar context list$ briar context list --prefix knowledge:$ briar context list --prefix plan:
$ briar context delete
briar context delete [--yes] BLOB_NAMERemove a blob. Prompts unless --yes.
$ briar context delete knowledge:acme.archive-2025q4 --yes
$ briar context categories
briar context categoriesPrint distinct category prefixes — e.g. knowledge, plan.
briar dashboard
Serve a read-only HTML status page summarising the droplet state: scheduler log, journal sessions, knowledge blobs, disk usage, secrets coverage. Designed to run alongside briar runbook serve on the same host.
--host ADDRESSdefault: 127.0.0.1--host 0.0.0.0 to expose publicly, but verify firewall + auth first.--port PORTdefault: 8080--examples DIRdefault: ./examples--knowledge-store {file,postgres}filepostgrespostgres if BRIAR_DATABASE_URL is set, else file.--knowledge PATHdefault: ./knowledge--knowledge-store=file).--log-file PATHdefault: /var/log/briar/scheduler.log--disk-path PATHdefault: /--repo-path PATHdefault: .--secrets-file PATHdefault: /etc/briar/secrets.envsecrets.env path. The dashboard surfaces names + lengths only — never values.--du-path PATH--journal-store {file}default: filefile--journal-root PATHdefault: ./journal--once$ briar dashboard \--host 0.0.0.0 --port 8080 \--examples runbooks/ \--knowledge knowledge/ \--repo-path /opt/briar-scheduler \--log-file /var/log/briar/scheduler.log
briar journal
Inspect decision-journal sessions recorded by every other briar command. Each session is a structured stream of events: extractor timings, LLM stop reasons, selector decisions, tool calls, PR URLs.
$ briar journal list
briar journal list [--store {file}] [--root PATH]
[--command FILTER] [--limit N]--store {file}default: filefile--root PATHdefault: ./journal--command PREFIXscaffold., plan.run., agent.implement.).--limit N$ briar journal list --command plan.run. --limit 5$ briar journal list --command agent.prfix.
$ briar journal show
briar journal show [--store {file}] [--root PATH] SESSION_IDPretty-print one session as markdown.
$ briar journal show 7a3b8c2d
$ briar journal export
briar journal export [--as {markdown,json}] [--out PATH] SESSION_IDWrite one session to a path.
--as {markdown,json}default: markdownmarkdownjson--as, not --format, so it doesn't collide with the global --format flag.)--out PATH- for stdout.$ briar journal export 7a3b8c2d --as json --out /tmp/last-run.json
briar version
Print the installed CLI version (briar-cli <semver>).
$ briar version
See also
- briar extract — populates the knowledge blobs that
context getreads. - briar telemetry preview — inspect the JSON event a journal session would emit (or not).