cc-broWhy is a signed-in worker “not allowed”?
Login and project permission are separate. In the project root, run cc-bro init to see the saved policy. Update the explicit list if needed. codex, pi:openai-codex and pi:deepseek are three different IDs. See Project allowlist.
Why can’t I change a worker’s model?
A name belongs to one native session. Use a new name to change worker or model. For pi, run pi --list-models and supply the complete provider/model-id from the permitted provider.
I closed the manager chat. Did the ticket stop?
Closing the chat does not stop the local runner. Use cc-bro ls, inspect cc-bro show NAME --json and run cc-bro wait NAME TURN for the outstanding turn. To cancel just that worker use cc-bro stop NAME.
Why can’t the reviewer see my latest edits?
A worktree starts from committed HEAD. Check the writer’s branch and files on the board. Wait for the correct turn, including any queued follow-up, and keep the writer’s checkout stable during review. See Worktrees and review.
Where do I enter a key or open the old manager room?
Sign in with your chosen worker CLI and open Claude Code in your actual project. The board’s Settings page opens the CLI login command; it does not collect keys. For an incompatible old runner, follow Upgrade from 0.1.0.
A listed model fails at runtime
A CLI catalog does not guarantee quota or account access. Inspect the error and select another allowed model explicitly. cc-bro does not buy credits or silently switch providers.
A custom worker has no cache or tool steps
That is the documented degraded capability level. Session continuity is trial-tested, while Git file summaries, reviews and worktrees still work.