Changelog

0.3.1

• The roster discovers all installed, signed-in CLI models and pi providers. Project permissions still apply. Hide model families globally or per project to remove them from the manager's roster and reject dispatch, including queued starts.
• Model descriptions, tiers, grades and task picks ship in the package. Override entries by ID in ~/.cc-bro/models.json. The skill checks input capabilities first, honors user notes and rules, and flags research older than 60 days.
• Model inputs are intersected with the CLI's actual transport. CLI-reported context and output limits take precedence over catalog API ceilings; missing data stays unknown. say --attach delivers supported images through native Codex or pi, with snapshots preserved for queued turns.
• Each bro can have a global default model and effort, with project overrides. The roster and Settings show effective defaults; subsequent dispatches use them without changing other CLI settings.
• Text and JSON rosters are compact by default. Denied bros contain only ID and permission; effort/fast variants share one row, and catalog-labeled older models are folded. Use --full for exact variants, limits and full metadata, or --worker ID to inspect one bro. Notes and rules remain intact.
• Bilingual Docs cover model capabilities, attachments, catalog overrides, hiding, defaults and compact queries.

Upgrade from 0.3.0

Install cc-bro@0.3.1, then run cc-bro shutdown and cc-bro setup to refresh the runner and skill. Let work you want to finish complete first: shutdown stops running and queued turns across all projects on that runner. Existing settings, sessions and tickets are preserved. JSON consumers should use roster --json --full when they need detailed model fields. Denied bros no longer expose models even in full mode; user-hidden models stay hidden. See the upgrade guide.

0.3.0

• A live project roster exposes permitted CLIs, models, effort levels, detected defaults, login, capabilities, rules and user notes. The Claude Code skill reads it before choosing a bro. say and review accept --effort and can change models between completed turns.
• Built-in agy and cursor-agent workers join native Codex and pi. They resume by explicit session ID and queue active follow-ups. Cache is shown only when the CLI reports it. Every backend can use worktrees and participate in linked reviews.
• Custom CLI templates provide new-session and resume commands, reply/ID extraction and optional model/effort arguments. A real two-turn memory trial is required before saving. Gemini CLI and OpenCode are editable, degraded presets rather than unverified full adapters.
• The board has global and project Settings: read-only detection, install/update/login commands opened in Terminal, allowlists, defaults, notes and rules. Manager-proposed notes need user confirmation. Settings are stored only in cc-bro; credential-file values and other CLI configuration are untouched.
• The website adds bilingual roster, custom CLI and Settings guides.

Upgrade from 0.2.0

Install cc-bro@0.3.0, then use the new cc-bro shutdown and rerun cc-bro setup. Wait first if you want active work to finish: shutdown cancels running and queued turns across the runner’s projects. Existing 0.2 policies, named sessions and ticket history are preserved; no new workers are allowed automatically. The old-runner shutdown path remains compatible with 0.1.0 and M2. See the upgrade guide.

0.2.0

Breaking: the manager room is gone

Open Claude Code in the project itself. The separate manager folder, its local skill and the board’s provider settings were part of 0.1.0. The new user-level skill delegates from the chat you already use. The new registry does not import 0.1.0 tickets or manager notes.

Workers and tickets

• Choose native Codex or a pi provider for each ticket. Register the allowed worker IDs and a default per project. Native Codex and pi using a Codex subscription are separate choices.
• Reuse a name to continue a session; use different names to run in parallel. A follow-up receipt says whether it reached the current turn, was queued for the next turn or was rejected.
• Start a ticket in a Git worktree or ask a different worker to review a completed turn. The board shows the branch, changed files, steps, linked reviews and reported input cache hits. Acceptance leaves the branch and worktree intact.

Upgrade from 0.1.0

1. Let any work you want to keep running finish. If you have notes in a manager room, keep that folder for reference.
2. Install with npm install -g cc-bro@0.2.0. If an old runner is active, use the new cc-bro shutdown. It stops running and queued work across that runner’s projects; unfinished turns do not resume automatically. Files already written stay on disk.
3. Run cc-bro setup. In the actual project root, run cc-bro init and choose allowed workers and a default. Open Claude Code there and type /cc-bro. The old ticket database stays on disk.

See the upgrade walkthrough.

0.1.0

The first macOS preview paired each project with a separate Claude Code manager room. Named pi workers ran in the project and continued working when the manager chat closed.

• The setup board could install pi, connect a provider using a key or subscription, and set the default worker model.
• Tickets moved through Queued, Working, Review and Done. The CLI could send follow-ups, show history, wait for a turn or stop a worker. The local board showed progress across projects.