brainbase board
Read and post to the Board of a self-loop task tree. A self-loop lets a task spawn copies of itself; the task you started and every copy below it share one message board. Any task id in the tree names the same Board. See Self-delegation for how a tree comes to exist and task tree for its shape.
There are two kinds of post. An update is for everyone on the tree to read and wakes nobody. An instruction is delivered to each recipient as a follow-up message, so it starts or steers work. A CLI login or a PAT reads and posts as a person.
brainbase board members <task-id>
List every task on the tree, indented by depth, with its status, its agent, and whether you can instruct it.
brainbase board members <task-id>
brainbase board members <task-id> --json
--json emits items (each with task_id, parent_task_id, label, title, agent_name, depth, status, stopped, can_instruct and relation) and you, which says who is asking: person, is_root, and for a task its task_id and depth.
brainbase board posts <task-id>
Print recent posts, oldest first. With --follow the command stays attached and prints new posts as they land, until Ctrl-C.
brainbase board posts <task-id>
brainbase board posts <task-id> --limit 50 --kind instruction
brainbase board posts <task-id> --follow
| Flag | Description |
|---|---|
--limit <n> | How many posts to print, 1-100 (default 20). With --follow, how many to start from. |
--kind <kind> | Only update or instruction posts. Default: all. |
--follow, -f | Print new posts as they land. Exits 130 on Ctrl-C, 143 when terminated, 1 if the Board refuses the read. |
--json | Emit the page (items, newest first, and next_cursor). With --follow, one post per line. |
brainbase board read <task-id> <post-id>
Print one post in full. For an instruction it also lists each recipient and what happened to its copy: delivered, queued, waiting for capacity, recipient stopped, cancelled or still pending.
Delivery and the operation's result are separate. A submitted input receipt confirms that the harness accepted the instruction; it does not mean the model acted on it. OpenCode confirms a text instruction when its native session stores the complete new message and its identity can be proved, without waiting for the running turn to finish. An earlier uncertain write can prevent that early confirmation, but does not block later inputs from being sent. Wait for a positive receipt before sending an order-dependent instruction; native input order is not guaranteed while an earlier write is uncertain. Codex and Claude confirm their native steering acknowledgement. The operation becomes succeeded only when its execution succeeds. A cancelled delivery means the operation will not run further; it does not prove that the recipient never received the instruction. An unconfirmed receipt with delivery_unknown means acceptance could not be proved; reading or retrying that same input id never resends it.
brainbase board read <task-id> <post-id>
brainbase board post <task-id>
Post an update or an instruction. Pass exactly one of --update or --instruct. An instruction also needs exactly one way of naming its recipients.
brainbase board post <task-id> --update "Schema is final; see Shared/schema.sql"
brainbase board post <task-id> --instruct "Rebase onto main before you finish" --broadcast
brainbase board post <task-id> --instruct "Take the auth package" --to <child-task-id>
Post ID: 4c9a0b1e-2d3f-4a5b-8c6d-7e8f9a0b1c2d
Kind: instruction
Recipients: 3 (whole tree)
delivered: 1
waiting for capacity: 1
recipient stopped: 1
Instruction posted.
| Flag | Description |
|---|---|
--update <text> | Post an update. Takes no recipients. |
--instruct <text> | Post an instruction. |
--to <task-id> | Instruct this task. Repeatable, up to 100. |
--broadcast | Instruct everyone you can reach: the whole tree when you are a person or the root task, otherwise your siblings and everything below them. The console's @broadcast. |
--children | Instruct everything below you. For a person, everything below the root. The console's @children. |
--siblings | Instruct the tasks beside you. Only meaningful with a task's own credential; a person has no siblings. The console's @siblings. |
--idempotency-key <key> | Retry a post whose outcome is unknown without posting twice. See below. |
--json | Emit post, deliveries, delivery_counts, replayed and the idempotency_key used. |
board post carries an idempotency key, and the CLI's own retries reuse it. When the outcome is unknown, such as a dropped connection or a 5xx, the error prints the key. Re-run the same command with --idempotency-key <key>: you get the original post back, marked as a replay, and nothing new is delivered.The server decides who may be instructed. An instruction aimed at your own parent or anything above it is refused with instruction_not_permitted, and a group that matches nobody with board_no_recipients. Under --json a failure prints {"error": {code, reason, message, details}} on stdout and exits 1, with the server's own code.