Upgrading from cc-bro (0.4.x) or opus-manager#
- If you have active turns you want to finish, check
cc-bro statusand wait for them to complete. - Install
broco, stop any legacy runner, and runbroco setup:
npm install -g broco
broco shutdown
broco setup --migrate-cc-brobroco shutdown cleanly stops older cc-bro runners across previous protocols (including legacy ~/.cc-bro socket paths).
Running broco setup --migrate-cc-bro losslessly copies your existing ~/.cc-bro/ state into ~/.broco/ without deleting ~/.cc-bro/ — keeping your registered projects, allowlists, defaults, notes, rules, stats, and ticket history intact while installing the new multi-host SKILL.md into ~/.agents/skills/broco/ and your detected coding agents.
What changed in 1.0.0#
- Package & paths: CLI command
broco, data directory~/.broco/($BROCO_HOME), optional per-repo directory.broco/, and environment variablesBROCO_*(includingBROCO_TZfor timezone overrides andBROCO_IN_WORKER=1for recursion protection). - L0 zero-
init: You no longer needinitin every repository; global policy works everywhere without creating dotfiles. Existing.broco/or migrated per-repo policies continue to override global defaults. - Built-in
claudeworker: Nativeclaudeis now a symmetric worker alongsidecodex,agy,cursor-agent,pi:<provider>, andcustom:<name>. Confirm whether you wantclaudein your global allowlist duringbroco setup. - Default cross-vendor
review:broco review <name>now auto-selects a different-vendor worker with quota headroom when--byis omitted. - Local timezone: Timestamps follow
BROCO_TZ→TZ→ your system timezone instead of hardcodingAsia/Shanghai.
Upgrading from 0.3.x or 0.2.x#
Install broco, let any active work finish, run broco shutdown, then run broco setup. Existing 0.2/0.3 policies, sessions, and tickets migrate into ~/.broco/ without broadening permissions. Scripts expecting full model metadata from roster --json should pass --full.
Upgrading from 0.1.0 (legacy manager rooms)#
Version 0.2.0 retired separate manager rooms. Keep any notes in old 0.1.0 manager folders for reference, install broco, run broco shutdown and broco setup, and work directly inside your real repository chats. See Your first ticket.