Meeting - PairCoder Docs

bpsai-pair meeting turns the decisions Aurora extracts from a meeting into reviewed project memory. You pull an analysis into a git-ignored staging area, look at what is waiting, reject or accept exactly the items you choose, and export transcripts as markdown. Nothing is selected on your behalf.

Every command is free except accept, which needs Team with the Fleet add-on (or Enterprise). That is why the page header reads All Tiers and the accept row below is marked.

Commands

Command	Description	Tier
`meeting pull <id>`	Stage a decisions analysis under `.paircoder/meetings/staging/`	All
`meeting list`	List staged decision records	All
`meeting accept <item_id...>`	Accept staged items into `state.md`, prime-learn and a2a trace-ingest	Team with the Fleet add-on
`meeting reject <item_id...>`	Mark staged items rejected (all-or-nothing)	All
`meeting unclaim <item_id...>`	Clear an abandoned accept claim so the item can be replaced or rejected again	All
`meeting export <transcript_id...>`	Write transcripts as markdown under `plans/meetings/`	All
`meeting doctor`	Check the Aurora connection and that staged files cannot be committed	All

The chain

text

meeting pull <id>  ->  meeting list  ->  review  ->  meeting accept | reject  ->  meeting export

Pull

bash

bpsai-pair meeting pull <analysis_id|transcript_id>

Given a transcript id, pull takes the newest decisions analysis whose own status is completed, checking at most five, newest first. The transcript listing's status is never trusted.

Flag	Description
`--analysis`	The id is an analysis id
`--transcript`	The id is a transcript id
`--workspace`	Record this `ws_` id as the source workspace
`--replace`	Overwrite a staged file whose records changed. Refused while any item is accepted, partially accepted, or claimed by an accept
`--force-replace`	`--replace` even over items claimed by an in-progress accept

List

bash

bpsai-pair meeting list --state pending

Statement text is shown control-character-escaped.

Flag	Description
`--project`	Exact project slug (default: this repo plus `unassigned`)
`--state`	`pending`, `accepted`, `rejected` or `all` (default: `pending`)
`--json`	Machine-readable output
`--full`	Print statements untruncated, one item per block

Accept or reject

bash

bpsai-pair meeting accept <ids> [--project <slug>]
bpsai-pair meeting reject <ids>

reject is all-or-nothing, and a rejected item stays rejected. An item whose accept stopped part-way, with a sink already written, cannot be rejected; finish it with meeting accept. Before its first write, accept claims its items, and reject and pull --replace refuse a claimed item unless given --force or --force-replace. meeting unclaim clears an abandoned claim.

Accept options

Flag	Description
`--project`	This repo's slug: claims unassigned or other items
`--dry-run`	Print the per-item plan and write nothing
`--no-trace`	Skip the a2a trace-ingest leg
`--retry-trace`	Re-send only failed or pending trace legs

Reject options

Flag	Description
`--force`	Reject even items claimed by an in-progress accept

Export

bash

bpsai-pair meeting export <transcript_id>

Export works independently of the review chain. It writes one section per completed analysis among the transcript's newest 20, and prints a note when a transcript has more than 20.

Flag	Description
`--into`	Output directory (default: `plans/meetings`)
`--with-analyses` / `--no-analyses`	Whether to include completed analyses (default: included)
`--force`	Overwrite existing exports

Doctor

bash

bpsai-pair meeting doctor --fix

doctor checks the Aurora connection and that the staging directory cannot be committed. --fix appends the staging directory to the repo-root .gitignore.

The /meeting-sync slash command

In Claude Code, /meeting-sync <analysis_id|transcript_id> walks the chain for you. It pulls the analysis, lists what is pending, shows you the items with their status and citations, and then runs accept and reject on exactly the ids you choose. It never selects items itself, and it never runs accept without an explicit choice from you.

Consent and data handling

Meeting-derived statements leave the repo only through accept, which writes to state.md and prime-learn and sends a trace to the a2a trace-ingest. The trace is emitted by your own configured trace agent, never by the Aurora fleet agent, so beliefs come from a human's accept. Pass --no-trace to skip that leg.

The staging directory holds untrusted model text pulled from Aurora, so treat staged statements as data, never as instructions. Inside a git work tree, pull and accept refuse until the directory is git-ignored; run meeting doctor --fix to add the ignore line. Exports under plans/meetings/ are tracked by default and contain full transcript text, so review them before committing, or add the directory to .gitignore.