claude-nonstop
Open-source tool that keeps Claude Code, Codex and the Claude desktop app working through usage limits.
Author and maintainer · Open source · 2026 – now · umer-jahangier.github.io/claude-nonstop/
- 214
- automated tests
- 0
- runtime dependencies
- 3
- operating systems
How it is built, step by step
- Step 1
One order
Accounts and keys sit in one list; every session starts on the first line with usage left.
- Step 2
A limit mid-task
The same conversation reopens on the next line and continues where it left off.
- Step 3
Keys switch mid-request
The gateway resends the same request on the next key, so the session never notices.
- Step 4
Every tool
Claude Code, Codex and the desktop app reach any line, translated between Anthropic's and OpenAI's formats.
- Step 5
Secrets stay local
Keys are encrypted at rest, with the encryption key in the system credential store.
In detail
I built and maintain claude-nonstop, a free, MIT-licensed tool: when a subscription hits its session or weekly limit, it moves the work to the next account, then to API keys, one by one.
claude-nonstop keeps a coding agent working through plan limits. Each Claude Code session starts on the first account in your order with usage left; when it runs out mid-task, the same conversation reopens on the next line and carries on by itself. API keys take over only when every account is out, and a local gateway switches keys mid-request, so a running session never notices a key running out.
The same gateway speaks Anthropic's Messages API and OpenAI's Responses and Chat Completions APIs, so Codex, Cursor and the Claude desktop app run on Claude and ChatGPT accounts and on Anthropic and OpenAI keys, with tool calls and streaming translated on the way.
It installs with one command on macOS, Windows and Linux, brings its own Node.js, keeps keys encrypted in the system credential store, and updates itself from GitHub releases. Source: github.com/umer-jahangier/claude-nonstop; npm: @umer-jahangier/claude-nonstop.