@brainbase-labs/cli 0.60.0 → 0.62.0

package/README.md

@@ -135,6 +135,13 @@ task's next turn runs on; a turn already running keeps its model.
 `--clear-model` returns the task to its agent's default model. See
 [the command reference](docs/reference/commands.mdx) for every flag.
 
+If a model you picked for a task is later retired, the task keeps running on
+its agent's default model, and `task create`, `task send` and `task get` print
+a warning on stderr until you decide: `brainbase task update <task-id>
+--clear-model` to use the agent default, or `brainbase task update <task-id>
+--model <id>` to pick another. Exit codes and stdout are unchanged, and
+`--json` carries the server's `model_notice`.
+
 ## Benchmark management
 
 `benchmark init`, `benchmark validate`, and command help are local and need no
@@ -281,10 +288,17 @@ output.
 
 The suite is version-sensitive too, so the pin is enforced at each entry point:
 `bun run verify` and `bun run build` refuse another Bun outright, and `bun test`
-prints a warning and carries on. Each names the pinned version and the command
-to get it: `npx bun@<pinned> …`. Use `npx` rather than `bunx` — bunx runs most
-published Bun versions but cannot resolve a bin for 1.3.10 specifically, which
-is the current pin. Set `SKIP_BUN_VERSION_CHECK=1` to override any of them.
+and `bun run test` print a warning and carry on. Each names the pinned version
+and the command to get it: `npx bun@<pinned> …`. Use `npx` rather than `bunx` —
+bunx runs most published Bun versions but cannot resolve a bin for 1.3.10
+specifically, which is the current pin. Set `SKIP_BUN_VERSION_CHECK=1` to
+override any of them.
+
+`bun run test` runs every test file in its own `bun test` process, half the
+cores' worth at a time (`--jobs N` or `BUN_TEST_JOBS` to change that; any other
+option goes to each `bun test`). `--shard i/n` runs every n-th file: CI splits
+the suite over six runners that way, one file at a time on each. A bare
+`bun test` runs the same files serially in one process.
 
 ### Releasing
 
@@ -328,10 +342,35 @@ older manifests keep their existing behavior.
 `runtime_mode` accepts `fixed` or `auto`, separately from the lead harness and
 model. An explicit value is synced by `agent create` or `agent push`; omission
 preserves the remote mode. A mode-aware control plane's pull writes `auto` and
-omits `fixed`.
+omits `fixed`. `brainbase agent runtime --mode fixed|auto` sets it directly.
 Runtime Auto requires the server's `self-delegation` feature flag, and children
-also need a self-edge in an orchestration. Legacy control planes refuse explicit
-mode writes. `agent pull --force` discards local runtime-mode edits.
+also need a self-edge in an orchestration. A control plane that does not report
+a mode runs every agent Fixed, so `runtime_mode: fixed` is always accepted and
+only `auto` is refused there. `agent pull --force` discards local runtime-mode
+edits.
+
+## Self-loops
+
+A self-loop lets an agent's task spawn copies of itself. Everything the web
+console does with them has a command:
+
+```sh
+brainbase orchestration self-loop builder      # let the agent spawn copies (--remove to undo)
+brainbase agent runtime --mode auto --children 8 --shared-folder on
+brainbase agent shared put ./brief.md inbox/   # files every copy can read at /workspace/Shared
+brainbase task tree <task-id>                  # the task, its copies, capacity, "waiting on children"
+brainbase task stop <task-id> --tree           # stop the task and everything below it
+brainbase board posts <task-id> --follow       # the tree's message board
+brainbase board post <task-id> --update "Schema is final"
+brainbase board post <task-id> --instruct "Rebase onto main" --broadcast
+brainbase task send <task-id> "Use this" --file ./notes.md
+```
+
+The shared folder is off on a new agent; without it, copies cannot hand files
+to each other. `board post --instruct` takes `--to <task-id>` (repeatable),
+`--broadcast`, `--children` or `--siblings`, and every post carries an
+idempotency key that a retry reuses, so nothing is delivered twice. See
+`docs/reference/commands.mdx` for each command.
 
 When `agent create` claims a manifest with no `default_model`, the control plane
 gives the agent the platform default for its harness, the same model the web