Skip to content

Autonomous development for real products. Governed agents build from specs you approve, follow the rules you set, and nothing merges until another agent proves it. Your decisions, judgement and taste are the bar that work must clear. Declare your vision and let agents build it.

Merge main into core/913

Corey Olsonf4deb154e0e0
diff --cc src/templates.js
index 1ea13272,f11da05a..8dd45b60
--- a/src/templates.js
+++ b/src/templates.js
@@@ -126,10 -126,8 +126,10 @@@ ${doctrineText(doctrine)
pullboard worktree <lane> --model "<model name>"
- It prints the folder to work in and what to run there first. Every join needs the exact model label, either with \`--model\` or the \`PULLBOARD_MODEL\` environment variable; family is separate and never supplies the model. A smaller model joins with \`--route light\` or \`--route mid\` and takes items at its tier and below. Work only in that folder. Your shell may start every command in the main checkout, where pullboard takes you for the coordinator, so begin each command with \`cd <your worktree> &&\`. Verifiers take the \`review\` lane, which owns no folders. Only the coordinator adds a lane, from the main checkout, once the person agrees: \`pullboard lane add <name> --owns <path>[,<path>]\`. \`pullboard init\` proposes lanes from the folder layout and writes none until the person accepts. Keep your worktree and branch until your items are merged.
+ It prints the folder to work in and what to run there first. Every join needs the exact model label, either with \`--model\` or the \`PULLBOARD_MODEL\` environment variable; family is separate and never supplies the model. A smaller model joins with \`--route light\` or \`--route mid\` and takes items at its tier and below. Work only in that folder. Your shell may start every command in the main checkout, where pullboard takes you for the coordinator, so begin each command with \`cd <your worktree> &&\`. Verifiers take the \`review\` lane, which owns no folders. Only the coordinator adds a lane, from the main checkout: \`pullboard lane add <name> --owns <path>[,<path>]\`. \`pullboard init\` proposes lanes from the folder layout; the coordinator adds those first lanes without waiting, then tells the person which lanes it made. After that, a change to which lane owns a path waits for the person's OK. Keep your worktree and branch until your items are merged.
+**Codex.** Codex's workspace-write sandbox keeps \`.git\` read-only, and the board lives in \`.git/pullboard\`, so start Codex with that folder writable before the first pullboard command: \`codex --add-dir "$(git rev-parse --path-format=absolute --git-common-dir)/pullboard"\` To keep it in \`~/.codex/config.toml\`: a permission profile takes \`"<that folder>" = "write"\` in its \`[permissions.<profile>.filesystem]\` table; only settings without a profile use \`writable_roots\` under \`[sandbox_workspace_write]\`, which a named profile ignores. A refused \`BOARD_NOT_WRITABLE\` names the same step.
+
**The loop.**
1. \`pullboard resume\` at the start of every session and after your context is compacted: your claim, what came back, unread shouts and the next step. Then \`pullboard inbox\`.
2. \`pullboard next\` claims the next free item your session can take across the lanes, by release and queue rank. It names the lane worktree to use and opens one when your session has none there; begin subsequent commands in that folder. Each worktree still owns only its lane’s files. Joining associates the seat with the invoking agent session automatically; no person setup is needed. When everything is waiting on other work, \`pullboard next --wait 9\` keeps looking for up to 9 minutes, which fits one tool call with a ten-minute timeout; run it again to keep waiting. A claim is a 2-hour lease; claim again to renew. The criterion freezes now: \`pullboard show <id>\` is the bar your work is judged against, and its brief says how to start. \`pullboard why <id>\` lists the decisions that changed it, newest first. When your own answer, verdict or fact changes other items, name them with \`--implies <ids>\` so each one carries it. A claim or submit refused as CRITERION_PROVES_NOTHING names a check that already passes on main, so it proves nothing: shout the coordinator for a check that fails before the work. Only the person accepts a check as it stands, with \`pullboard check accept <id>\` from the main checkout or the view.