CLI reference
briar plan
Flags common to every subcommand
Every plan subcommand accepts these four flags. They are documented once here and elided from each subcommand below.
--store {file,postgres}default: filefilepostgres--root PATHdefault: ./knowledge--store=file).--company COMPANYknowledge:<company>.<plan>).--journal-store {file}default: filefilestatus, next, and run to read past decisions.--journal-root PATHdefault: ./journal$ briar plan build
briar plan build [--name NAME] [--default-branch BRANCH]
[--max-cards N] [--with-knowledge] [--print] [--dry-run]
[--llm {anthropic,openai,gemini,bedrock}] [--model MODEL]
BOARDFetch a tracker board and persist an ordered implementation plan. Cards get LLM-annotated with scope, out-of-scope, risks, and inferred dependencies.
board URL | jira:KEYrequiredjira:KAN).--name SLUG--default-branch BRANCHdefault: main--max-cards Ndefault: 50--with-knowledgeknowledge:<company>) and active-tickets blob into each card's synthesis context.--print--dry-run--print.--llm PROVIDERanthropicopenaigeminibedrock--model MODELclaude-sonnet-4-6).$ briar plan build jira:KAN --name q3 --company acme \--llm anthropic --with-knowledge
$ briar plan show
briar plan show NAMEPrint the markdown body of a stored plan to stdout.
namerequired$ briar plan show q3 --company acme | less
$ briar plan status
briar plan status NAMEShow past / current / to-be-done cards with the journal artifacts each one produced. The quick at-a-glance view of plan progress.
namerequired$ briar plan status q3 --company acme
$ briar plan next
briar plan next --llm {anthropic,openai,gemini,bedrock}
[--model MODEL] NAMEAsk the LLM selector what to do next; print the decision (card key + rationale) without executing. Useful for previewing a run.
namerequired--llm PROVIDERrequiredanthropicopenaigeminibedrock--model MODEL$ briar plan next q3 --llm anthropic --company acme
$ briar plan advance
briar plan advance --card CARD
[--status {pending,in_progress,done,blocked}] NAMEMark a card with a chosen status manually. Useful when you completed a card outside Briar (a human PR) and want the plan to reflect reality.
namerequired--card CARD_KEYrequired--status STATUSdefault: donependingin_progressdoneblocked$ briar plan advance q3 --card KAN-7 --status done --company acme$ briar plan advance q3 --card KAN-9 --status blocked --company acme
$ briar plan list
briar plan listList stored plans in the configured store.
$ briar plan list --company acme
$ briar plan clear
briar plan clear [--yes] NAMERemove a plan from the store. Prompts unless --yes.
namerequired--yes$ briar plan clear q3 --company acme --yes
$ briar plan run
briar plan run --llm PROVIDER --owner OWNER --repo REPO
[--limit N] [--continue-on-failure] [--max-replans N]
[--tracker {...}] [--provider {...}]
[--meeting* flags] [--knowledge PATH] [--runbook YAML]
[--git-user-name NAME] [--git-user-email EMAIL]
[--keep-worktree] [--dry-run] [--max-iter N] NAMEThe headline command. Iterates the LLM selector: pick → implement → writeback, with REPLAN actions allowed up to --max-replans. Continues until the plan is done, --limit is hit, or a card fails (unless --continue-on-failure).
Positional
namerequiredLoop control
--limit Ndefault: 00 = unlimited).--continue-on-failureblocked and continue. Default: stop.--max-replans Ndefault: 3--max-iter Nagent implement).--dry-run--dry-run to every implement call.--keep-worktreeTarget repo + tracker
--owner OWNERrequired--repo REPOrequired--tracker-project KEYagent implement. Defaults to <owner>/<repo>.--tracker {bitbucket-issues,github-issues,jira,linear}default: github-issuesbitbucket-issuesgithub-issuesjiralinear--provider {bitbucket,github}default: githubbitbucketgithub--git-user-name NAME--git-user-email EMAILContext wiring
--knowledge PATHagent implement (postgres ignores).--runbook YAMLmessages: block, so the agent knows where to write outbound comments.--meeting PROVIDERfireflies--meeting-key ID--meeting-query STRING--meeting-top-k N--meeting-max-bytes NLLM
--llm PROVIDERrequiredanthropicopenaigeminibedrock--model MODEL$ briar plan run q3 --company acme --llm anthropic \--owner acme --repo widgets \--tracker jira --tracker-project KAN \--runbook runbooks/acme.yaml \--limit 5 --continue-on-failure
LLM cost shows up here
--limit liberally during your first runs. briar telemetry preview does not estimate cost; that's on your provider dashboard.See also
- briar agent — what
plan runcalls under the hood. - briar journal — inspect the decisions the selector made.
- Core concepts: Plans — the mental model behind selectors, replans, and writeback.