ccb
Run the official Claude Code through a claude-code-bridge gateway.
Get started
npm install -g --allow-scripts=@rimuruchan/ccb @rimuruchan/ccb
ccb login --gateway https://your-gateway.example
ccb account
ccb
Approve the device in your browser, then select an account your administrator has granted you access to.
CCB downloads and verifies Claude Code 2.1.295 from Anthropic on the first launch. Your Claude configuration, conversation history and plugins remain available.
Commands
| Command | Purpose |
|---|---|
ccb -c | Continue the most recent conversation |
ccb -r | Choose a conversation to resume |
ccb account | Switch accounts |
ccb status | Check your connection and runtime |
ccb login --renew | Renew device authorization |
ccb update | Update ccb and install or repair Claude Code |
ccb --help | Show all CCB commands |
ccb updates itself in the background with npm install -g, like Claude Code; ccb update does it now, and CCB_DISABLE_AUTOUPDATE=1 turns it off. The Claude Code version is maintained by CCB releases.
Installation notes
The platform package supplies a native CCB executable. The postinstall step links it to bin/ccb.exe, so CCB starts without Node. Claude Code is downloaded separately and verified against the official manifest and CCB's built-in checksum.
Recent npm releases run a package's install scripts only when they are allowed by name, and warn about the rest; --allow-scripts=@rimuruchan/ccb in the install command allows this one. npm 10 accepts the option too.
If npm install scripts are disabled, run the installed package's install.cjs once:
node "$(npm root -g)/@rimuruchan/ccb/install.cjs"
You can also run CCB through the package's cli-wrapper.cjs using Node.