Claude Code usage limit: how to keep working when you hit it
When Claude Code says You've hit your session limit or weekly limit, you can wait for the reset, switch to another Claude account, or continue on an API key. claude-nonstop does the switching for you: it reopens the same conversation on the next account in your order, then on your API keys, and Claude continues where it left off.
What the limits are
A Claude subscription has a session limit, a rolling usage window of about five hours, and a weekly limit. When either runs out, Claude Code stops the current turn and shows when it resets, for example You've hit your session limit · resets 3:45pm. How much you get depends on your plan and on how heavy the work is.
Your options when you hit one
- Wait for the reset. Recent Claude Code versions can continue the task by themselves at the reset if you leave the session open.
- Use another account. Claude Code supports several sign-ins through separate configuration folders (
CLAUDE_CONFIG_DIR). Switching by hand means quitting, changing folders and resuming. - Use an API key. API usage is billed per token and has no session limit, only your organisation's rate limits and credit.
- Automate it with claude-nonstop. It checks which account still has usage before each session, moves a stopped session to the next line, and falls back to your API keys only when every account is out.
Set it up with claude-nonstop
- Install it with one command. It brings its own Node.js and installs Claude Code if you don't have it.
# macOS and Linux curl -fsSL https://raw.githubusercontent.com/umer-jahangier/claude-nonstop/main/install.sh | sh # Windows (PowerShell) irm https://raw.githubusercontent.com/umer-jahangier/claude-nonstop/main/install.ps1 | iex - The web page opens. Your normal Claude Code login is already there as Main account. Click Add Account… for each extra Claude subscription and sign in on Anthropic's own page.
- Optionally click Add API Key… and paste a key. Keys are used only after every account is out.
- Open a new terminal and run
claudeas usual.
What happens at the limit
claude-nonstop starts Claude Code with a few documented hooks. When a turn stops on a usage limit, it checks the next lines in your order, and if one has usage it runs claude --resume <session> "Continue where you left off." on that line, keeping the flags you started with. Claude Code restarts for a moment, then the work carries on.
When an account above the keys has usage again, the session moves back to it after Claude finishes its current turn, so you don't keep spending API credit. With nothing left at all, it waits for the reset and continues by itself.
Questions
How long does the Claude Code session limit last?
The session limit is a rolling window of about five hours from your first message in it. Claude Code shows the exact reset time when you hit it.
Can I continue the same conversation on another account?
Yes. Claude Code's history lives on your computer, so claude --resume can reopen a conversation under another sign-in. claude-nonstop shares one history across all your accounts and does the resume for you.
Do I need API keys?
No. With only subscription accounts, claude-nonstop moves from one to the next. Keys are an optional fallback for when every account is out.
By Muhammad Umer (Umer Jahangier), author of claude-nonstop · Updated