No description
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
xicv f003036954 feat: add cc-continue (ccc) 0.1.0
Continue a Claude Code session on another of your Claude accounts when one
hits its usage limit, by resuming the same transcript under that account's
own login. No proxy, no credential handling.

- ccc setup, go, status, doctor and the StopFailure hook
- 110 tests on synthetic fixtures with a fake claude on PATH
2026-10-11 20:24:26 +10:30
src feat: add cc-continue (ccc) 0.1.0 2026-10-11 20:24:26 +10:30
tests feat: add cc-continue (ccc) 0.1.0 2026-10-11 20:24:26 +10:30
.gitignore feat: add cc-continue (ccc) 0.1.0 2026-10-11 20:24:26 +10:30
Cargo.lock feat: add cc-continue (ccc) 0.1.0 2026-10-11 20:24:26 +10:30
Cargo.toml feat: add cc-continue (ccc) 0.1.0 2026-10-11 20:24:26 +10:30
LICENSE-APACHE feat: add cc-continue (ccc) 0.1.0 2026-10-11 20:24:26 +10:30
LICENSE-MIT feat: add cc-continue (ccc) 0.1.0 2026-10-11 20:24:26 +10:30
README.md feat: add cc-continue (ccc) 0.1.0 2026-10-11 20:24:26 +10:30

cc-continue (ccc)

Continue a Claude Code session on another of your own Claude accounts when one hits its usage limit.

ccc does not proxy anything and never touches a credential. Each account keeps its own official claude login in its own config folder; the accounts share their transcripts through a symlinked projects/ folder. When a session stops on a usage limit, ccc go resumes the same session ID under another account, after checking that the original copy is closed and that the new process really runs as the target account.

Install

cargo install cc-continue

Unix only (macOS, Linux). Needs the claude CLI on PATH.

Set up

ccc setup

The wizard:

  1. records your primary account (the CLAUDE_CONFIG_DIR your shell uses, or unset);
  2. adds another account: creates its config folder with links to the primary's projects/, tasks/, settings.json, CLAUDE.md, hooks/, skills/, rules/, agents/ and commands/, then prints the one command you run to log it in (ccc never logs in for you);
  3. records each account's login (email and organisation) once you have logged in;
  4. optionally copies chosen MCP servers between accounts (names and key names are shown, never values);
  5. installs a StopFailure hook so a usage-limit stop is noticed and recorded.

Use

When a session stops on its limit you get a notification. Close that session, then:

ccc go                 # continue the newest stopped session on another account
ccc go <session-id>    # or a specific one, e.g. to go back after the limit resets
ccc status             # accounts, limits and stopped sessions
ccc doctor             # check links, logins, the hook and settings

ccc go restores the working directory and Claude.app's extra directories, and launches with bypassPermissions unless you pass --permission-mode MODE (or set permission_mode in ~/.config/cc-continue/config.json). The first turn on the other account re-reads the whole conversation without a prompt cache, so it is slower and uses more of that account's allowance.

Files

  • ~/.config/cc-continue/config.json: your accounts (names and folders are yours to choose).
  • ~/.local/state/cc-continue/state.json: limits and stopped sessions.

Both follow XDG_CONFIG_HOME / XDG_STATE_HOME.

Before relying on it

Check that using more than one personal subscription this way fits Anthropic's current terms for your accounts. The official way to keep going on one account is usage credits.

Licence

Licensed under either of Apache License, Version 2.0 or MIT licence at your option.