Show HN: Limitbreak – Claude Code switches accounts mid-session on a limit A developer released Limitbreak, an open-source local proxy written as a single Go binary using only the standard library, that lets one Claude Code install rotate across multiple Claude accounts when an account's 5-hour or weekly usage window is exhausted. The proxy sits at 127.0.0.1:48617 between the claude client and api.anthropic.com, and only switches accounts on a 429 response carrying the anthropic-ratelimit-unified-status: rejected header, marking that account spent until its reset time and replaying the same request on the next account before Claude Code sees the error. Limitbreak requires Go 1.22+ to build, runs on macOS or Linux, sends only /v1/messages* requests on an account's token while routing connectors, MCP and artifacts through Claude Code's own credentials, and reads logins from the macOS Keychain or each ~/.claude- config directory's .credentials.json. ★ L I M I T B R E A K ★ ADA ██████████ LIMIT → spent GRACE ░░░░░░░░░░ ready → takes the hit Use several Claude accounts from one Claude Code install, and switch between them automatically when an account's usage limit is hit, without restarting the session or losing its history. A small local proxy a single Go binary, standard library only, a few MB of RAM sits between claude and Anthropic's API. It sends each request on the active account's own login. When Anthropic answers that the account's 5-hour or weekly window is spent, the proxy remembers that account until its reset time and replays the same request on the next account before Claude Code ever sees the error. To the session nothing happened. claude ──ANTHROPIC BASE URL──▶ proxy 127.0.0.1:48617 ──▶ api.anthropic.com │ active account's token └─ 429 "rejected"? mark spent, retry on the next account Try it without touching any real login: limitbreak video plays a simulated switch in your terminal as a little arcade battle. git clone https://github.com/radu2lupu/limitbreak && cd limitbreak ./install.sh builds and starts the background service echo 'source "$HOME/.local/bin/limitbreak-shell.sh"' ~/.zshrc or ~/.bashrc limitbreak add sign in another account browser , repeat per account Open a new terminal and run claude as usual. When one account's limit is hit, the next one answers. - Only /v1/messages requests are sent on an account's token. Everything else claude.ai connectors, MCP, artifacts, profile goes through untouched with Claude Code's own credentials, so those keep working. - It never sets CLAUDE CODE OAUTH TOKEN that makes Claude Code drop its connectors and local MCP servers . - Accounts are the logins Claude Code already holds: the default one plus every ~/.claude-