Start with:
cb doctorcb doctor is read-only. It checks Python, Claude/Codex/Band credentials, git, gh, config files, expected agent roles, workspace writability, Band.ai connectivity, and the active memory backend.
Run:
cb init --repo <url>Register agents:
cb setup-agentsOn free-tier Band.ai, manually create the agents and write agent_config.yaml. See Configuration.
Add this to .env:
BAND_API_KEY=band_u_...Your Band.ai account likely does not have access to the agent-registration API. Use manual registration.
Run:
cb doctorThen check Authentication for credential precedence. Most failures are caused by missing framework CLIs, expired local login, missing API keys in Docker, or quota/rate-limit issues.
Coders reconnect via WorkerSupervisor. Check:
cb log --agent coder-claude_sdk-0Also inspect the worker state file under the configured workspace, for example:
.codeband/state/coder-claude_sdk-0.jsonTune restart pacing in codeband.yaml:
agents:
coders:
claude_sdk:
restart_delay_seconds: 5.0Watch the live feed:
cb feed --no-thoughtsThe Watchdog nudges idle agents after stale_threshold_seconds and escalates to the Conductor if progress does not resume.
Inspect worktrees:
git -C .codeband/repo.git worktree listRemove a broken worktree:
git -C .codeband/repo.git worktree remove --force <path>If local state is disposable, delete the workspace and let Codeband rebuild it on the next run.
cb up needs the Docker assets from the source repository. If you installed Codeband from PyPI (via uv tool, pipx, or pip), clone the repository and run from that checkout, or copy the docker/ directory into your project.
Git operations time out after 120 seconds. For large repositories, test the remote directly:
git clone --bare <url> /tmp/codeband-test.gitOnly these framework keys are supported:
claude_sdkcodex
Check pool entries in codeband.yaml and keys in agent_config.yaml.
- Run
cb doctor. - Confirm
.envis loaded in the same shell or container where Codeband runs. - Confirm
agent_config.yamlkeys matchcodeband.yaml. - Confirm
gh auth statusworks for the target repository. - Confirm the memory backend matches your deployment mode.
- Check
cb feed --no-thoughtsandcb log.