Summary: Most Claude Code problems fall into four groups: the claude command is not found after install, sign-in fails or keeps expiring, a stray API key quietly overrides your subscription, or you hit a usage limit or a server-side error. This guide matches the exact message you see to the fix Anthropic's own docs recommend, and explains which errors are your quota and which are not. Everything here was checked against the official Claude Code docs and the Claude pricing page on the date at the bottom.
First, read the message, not the symptom
Claude Code is unusually specific about its errors. "Not working" can mean six different things, and the fix for one can make another worse. For example, switching models fixes an Opus limit but does nothing for a weekly limit, and logging in again fixes an expired token but not an old ANTHROPIC_API_KEY sitting in your shell profile. So before trying anything, copy the exact line Claude Code printed and find it in the sections below.
Two commands help in almost every case, and both are mentioned throughout the official troubleshooting pages:
/statusinside a session shows which credential is actually active (your subscription login or an API key).claude doctorfrom your shell runs installation and environment checks, including keychain access on macOS.
1. "command not found: claude" after installing
This is the most common install complaint, and it is almost always a PATH problem rather than a failed install. The native installer puts the launcher at ~/.local/bin/claude on macOS and Linux, and at %USERPROFILE%\.local\bin\claude.exe on Windows. If that folder is not on your PATH, the shell cannot find the program even though it is there.
Fix on macOS and Linux
- Check the file exists:
ls -la ~/.local/bin/claude. A native install shows a symlink into~/.local/share/claude/versions/. - Add the folder to your shell's config file. For zsh:
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc, thensource ~/.zshrc. For Bash on Linux use~/.bashrc. - On macOS with Bash, use
~/.bash_profileinstead. Terminal on macOS starts Bash as a login shell, which ignores~/.bashrc. This catches a lot of people. - Open a brand new terminal and run
claude --version.
If it still fails, the docs list three usual causes: the terminal window was already open before the change, the line never got saved (check with grep -n '.local/bin' ~/.zshrc), or you edited the wrong shell's file (check with echo $0). A terminal inside VS Code or another editor inherits the editor's PATH, so quit and reopen the editor itself, not just the terminal tab.
Fix on Windows
In PowerShell, Test-Path "$env:USERPROFILE\.local\bin\claude.exe" tells you whether the native install is there. If it returns True but claude is still not found, add %USERPROFILE%\.local\bin to your User PATH (the docs give a two-line SetEnvironmentVariable command) and restart the terminal. Also watch for the shell mix-up errors: irm is not recognized or 'bash' is not recognized as the name of a cmdlet mean you pasted the install command meant for a different shell.
Two installs fighting each other
If you installed with npm years ago and later used the native installer, you can end up with two versions. Run which -a claude (or where.exe claude on Windows) to list every copy on your PATH. The docs recommend keeping only the native install and removing the others, for example npm uninstall -g @anthropic-ai/claude-code for an old global npm install, or brew uninstall --cask claude-code for Homebrew.
2. Install script errors that look scary but are not
A few install failures print confusing text. The official error table maps them like this:
syntax error near unexpected token '<'(or HTML/CSS in a PowerShell parse error): the install URL returned a web page instead of a script, often because a proxy or network filter intercepted it.curl: (22) ... error: 403: usually a proxy blocking the download host, or Claude Code not being available in your region.Killedduring install on Linux: the machine ran out of memory. Free memory or add swap, then rerun the installer.TLS connect errororunable to get local issuer certificate: update CA certificates, or configure your company's CA certificate if you are behind a corporate proxy.
To test the network quickly, the docs suggest curl -sI https://downloads.claude.ai/claude-code-releases/latest. A 200 on the first line means you can reach the download server. Behind a corporate proxy, set HTTPS_PROXY and HTTP_PROXY before installing.
3. Login fails, or you are asked to log in again and again
The universal reset
When the cause is unclear, Anthropic's first suggestion is a clean re-login: run /logout, close Claude Code, start claude again and finish the sign-in. If the browser does not open, press c to copy the login URL and paste it into a browser yourself.
"OAuth error: Invalid code"
The code expired or got cut off when you copied it. Retry and finish the browser step quickly. Over SSH, the browser may try to open on the remote machine, so copy the URL from the terminal and open it on your own computer.
Login breaks in WSL2, SSH or a container
If the browser shows a connection error for a localhost address, you do not need to fix networking. Copy the login URL the terminal shows, sign in on your local browser, and paste the code it gives you at the Paste code here prompt. If pasting into the prompt does nothing, run claude auth login instead, which reads the code more reliably.
Logged out after every session
Check your system clock first, since token validation depends on correct timestamps. On macOS, a locked or out-of-sync login Keychain can stop Claude Code from saving your login securely; claude doctor reports this as macOS Keychain is not writable, and unlocking the Keychain usually clears it.
"API Error: 403 Request not allowed" right after login
For Pro, Max or Ultra users, confirm the subscription is actually active in your claude.ai settings. For Console (API) users, an admin must give your account the "Claude Code" or "Developer" role. Corporate proxies can also cause this.
4. The hidden culprit: an old ANTHROPIC_API_KEY
This one deserves its own section because it produces several different-looking errors. When an ANTHROPIC_API_KEY environment variable is set and you have approved it, Claude Code uses that key instead of your subscription login. In non-interactive mode with -p, the key is always used when present. So a key left over from an old job or side project can cause:
API Error: 400 ... "This organization has been disabled"even though your subscription is fine;Credit balance is too lowon a paid Pro or Max plan;Request rejected (429)because requests go through a low-tier API key;Invalid API key · Fix external API key.
Fix: run /status and look at which credential is active. If it is an API key you did not mean to use, run unset ANTHROPIC_API_KEY (PowerShell: Remove-Item Env:ANTHROPIC_API_KEY), delete the export line from ~/.zshrc, ~/.bashrc or ~/.profile, and start claude again. The docs also warn that tools like direnv, dotenv plugins and IDE terminals can load a stale key from a project .env file, so check with env | grep ANTHROPIC in the same terminal where you launch Claude Code.
5. Usage limits: which ones are really your quota
Subscription plans have a rolling allowance, and when it runs out you see a message such as You've hit your session limit · resets 3:45pm or You've hit your weekly limit · resets Mon 12:00am. What you can do depends on which limit it names:
- Session or weekly limit: these are shared across all models, so switching models does not help. Wait for the reset time, or buy extra usage with
/usage-creditson Pro, Max and Ultra. Usage counts against the session and weekly windows at the same time, so one heavy burst can use up the week. - Opus limit or Sonnet limit: these apply to one model family only. Run
/modeland pick a model outside that family to keep working. Expect the next request to be slower, because each model has its own prompt cache. - Monthly spend limit: raise it in your claude.ai usage settings, or on Team and Enterprise ask an admin.
Run /usage at any time to see your plan's windows and when each resets.
Errors that are NOT your limit
API Error: Repeated 529 Overloaded errors: the API is at capacity for everyone. The docs state plainly that a 529 does not count against your quota. Wait a few minutes, check status.claude.com, or switch models with/model, since capacity is tracked per model.Server is temporarily limiting requests (not your usage limit): a short throttle; wait briefly and retry.API Error: 500: a server-side failure, not caused by your prompt or account. Your message stays in the conversation, so you can just typetry again.
6. Claude Code hangs, freezes or loops
If a command seems stuck, press Ctrl+C. If that does nothing, close the terminal. You do not lose the conversation: run claude --resume in the same folder to pick it back up.
If you see Autocompact is thrashing, a large file or tool output keeps refilling the context window right after compaction. The documented fixes are to ask Claude to read the file in smaller pieces, run /compact with a focus (for example /compact keep only the plan and the diff), move the big-file work to a subagent, or /clear if you no longer need the earlier conversation.
Which plan includes Claude Code?
A surprising number of "it won't let me use Claude Code" reports come from the Free plan, which does not include it. Here is how the consumer plans compare on the official pricing page:
| Plan | Price | Claude Code | Usage allowance | Extras worth knowing |
|---|---|---|---|---|
| Free | $0 | No | Limited, every 5 hours and every week | Chat, web search, file creation; no Opus |
| Pro | $20/month monthly, or $17/month billed annually ($200 up front) | Yes | 1x baseline, every 5 hours and every week | Usage credits available for extra usage |
| Max | $100/month | Yes | 5x Pro, every 5 hours and every week | $100/month in API credits; priority access at high traffic times |
| Ultra | $200/month | Yes | 10x Pro every week; no 5-hour limit for verified accounts | $200/month in API credits |
Prices exclude tax, and Anthropic notes that how fast you reach a limit depends on the model, chat length and file size. If you use Claude Code with a Console API key instead, you pay per token from prepaid credits, and Credit balance is too low means that balance is empty.
Editor's note
Who this is for: developers on Pro, Max or Ultra who installed Claude Code and hit a wall in the first days, and Console users whose team just rolled it out.
Who it is not for: Free plan users (Claude Code is not included), and people routing through Amazon Bedrock, Google Cloud or Microsoft Foundry, whose credential errors have separate sections in the official error reference.
Gotchas I noticed while checking the docs: the macOS Bash file trap (~/.bash_profile, not ~/.bashrc); the stray ANTHROPIC_API_KEY that can make a paid subscriber see "Credit balance is too low"; and the fact that switching models helps with Opus/Sonnet limits and 529 overloads but not with session or weekly limits. If something breaks after an update, claude --version is worth checking first, because several documented bugs are tied to specific older versions.
FAQ
Does a 529 Overloaded error use up my Claude Code limit?
No. The official error reference says a 529 means the API is at capacity for all users and does not count against your quota. Retry later or switch models.
Why does Claude Code say my credit balance is too low when I pay for Max?
Most likely an ANTHROPIC_API_KEY in your environment is routing requests through a Console account with no credits. Check /status, unset the variable, remove it from your shell profile, and run /login if needed.
Can I use Claude Code on the free Claude plan?
No. The Claude pricing page lists Claude Code for Pro, Max and Ultra, not Free. The alternative is paying per token with a Console API key.
Related guides on this blog
- Codex CLI Not Working? Fixes for Login, Sandbox and Limits
- Aider Not Working? Fixes for Edit, Token and API Key Errors
- Antigravity CLI Setup: Move From Gemini CLI Step by Step
Match the exact message to its section, check /status before anything else, and most Claude Code errors take minutes, not hours, to clear.
Images: own screenshots of the official Claude pricing page and Claude Code docs (claude.com, code.claude.com); see them at the end of this post.
Last verified: 2026-11-02
Sources:
Claude Code docs: Troubleshoot installation and login
Claude Code docs: Error reference
Claude Code docs: Troubleshooting
Claude pricing
댓글
댓글 쓰기