기본 콘텐츠로 건너뛰기

Claude Code Errors Fixed: Login, PATH, 429 and Usage Limits

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:

  • /status inside a session shows which credential is actually active (your subscription login or an API key).
  • claude doctor from 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

  1. Check the file exists: ls -la ~/.local/bin/claude. A native install shows a symlink into ~/.local/share/claude/versions/.
  2. Add the folder to your shell's config file. For zsh: echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc, then source ~/.zshrc. For Bash on Linux use ~/.bashrc.
  3. On macOS with Bash, use ~/.bash_profile instead. Terminal on macOS starts Bash as a login shell, which ignores ~/.bashrc. This catches a lot of people.
  4. 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.
  • Killed during install on Linux: the machine ran out of memory. Free memory or add swap, then rerun the installer.
  • TLS connect error or unable 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 low on 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-credits on 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 /model and 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 type try 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

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

Uploaded Image Uploaded Image Uploaded Image Uploaded Image Uploaded Image

댓글

이 블로그의 인기 게시물

브루(Vrew) 요금제 정리: 무료 200크레딧으로 어디까지 쓸 수 있나

요약: 영상 자막 편집기 브루(Vrew)는 2026년 4월 22일부터 기능별 사용량 대신 '통합 크레딧' 하나로 요금을 매겨요. 무료 플랜은 매달 200크레딧이 들어오는데, 음성 분석(자동 자막)만 쓰면 최대 200분 분량이라 짧은 영상 몇 편은 충분하지만, 영상 초반의 Vrew 마크를 지우려면 유료 플랜이 필요해요. 이 글은 브루 공식 가격 페이지와 고객센터 공지를 2026년 10월 23일에 다시 확인해, 크레딧 계산법과 플랜 고르는 기준을 정리했어요. 목차 브루 요금 구조: 통합 크레딧이란 1크레딧으로 할 수 있는 일 무료 플랜으로 되는 것과 안 되는 것 유료 플랜 4종 비교표 월 구독·연 구독·기간 이용권, 무엇이 이득일까 상황별 추천: 학생·직장인·유튜버 크레딧이 모자랄 때: 사용 기록 지우개 업그레이드·환불 전에 알아둘 규칙 운영자 메모, 자주 묻는 질문 1. 브루 요금 구조: 통합 크레딧이란 예전 브루는 플랜마다 음성 분석 몇 분, AI 목소리 몇 자, 번역 몇 자처럼 기능별 한도를 따로 줬어요. 그런데 보이저엑스(브루 운영사)가 실제 이용 데이터를 보니 한두 가지 기능만 집중해서 쓰는 사람이 훨씬 많았다고 해요. 그래서 2026년 4월 22일 업데이트부터는 플랜마다 정해진 크레딧을 받고, 어떤 기능에 쓸지는 내가 정하는 방식으로 바뀌었어요. 플랜별 매달 지급량은 Free 200 · Light 2,000 · Standard 10,000 · Business 12,000크레딧 이에요. 공식 공지에 따르면 무료 사용자는 매달 1일에, 유료 사용자는 매월 결제일에 충전되고, 남은 크레딧은 다음 달로 넘어가지 않아요. 바뀐 뒤 무엇이 좋아졌나 공지에 나온 예시가 이해하기 쉬워요. Standard 플랜에서 AI 목소리만 쓰면 예전에는 최대 50만 자였지만, 지금은 1만 크레딧을 모두 AI 목소리에 몰아 쓸 수 있어 최대 100만 자가 돼요. 반대로 여러 기능을 골고루 쓰는 사람은 크레딧이 기능끼리 ...

에이닷 전화 vs 익시오: 통화 녹음·AI 요약, 내 통신사·폰에 맞는 앱 고르기

요약: 통화 녹음과 AI 요약을 쓰고 싶다면 먼저 내 통신사와 휴대폰 종류부터 확인해야 해요. LG유플러스 고객은 무료 앱 익시오, SKT 고객은 에이닷 전화가 가장 기능이 많고, 다른 통신사의 아이폰 사용자는 iOS에 들어 있는 기본 통화 녹음·전사 기능이 현실적인 선택이에요. 이 글은 2026-10-30에 SKT·LG유플러스·Apple 공식 페이지와 도움말을 직접 확인해 세 가지를 비교했어요. 왜 '앱 기능'보다 '내 조건'을 먼저 봐야 할까요 통화 요약 앱 비교 글을 보면 기능 목록부터 나열하는 경우가 많아요. 그런데 실제로 써 보려는 사람에게 가장 먼저 걸리는 건 기능이 아니라 이용 조건 이에요. 익시오는 LG유플러스 고객 전용이고, 에이닷 전화는 누구나 설치할 수 있지만 통역콜·baro 같은 기능은 SKT 고객에게만 열려 있어요. 아이폰은 운영체제 구조상 앱이 통화를 마음대로 녹음하기 어려워서, 통신사 앱이 안 되면 iOS 기본 기능에 기대야 해요. 그래서 이 글은 "어떤 앱이 제일 좋은가"보다 "내 통신사·내 폰에서 무엇을 쓸 수 있나" 순서로 정리했어요. 기능 차이는 그다음이에요. 한눈에 비교: 에이닷 전화 vs 익시오 vs 아이폰 기본 통화 녹음 구분 에이닷 전화 (SKT) 익시오 ixi-O (LG유플러스) 아이폰 기본 통화 녹음 (Apple) 누가 쓸 수 있나 통신사 구분 없이 앱 설치 가능. 단, 통역콜·baro·그룹통화 발신 등은 SKT 고객 전용 U+ 모바일 고객. 타 통신사, 만 14세 미만, 선불요금제 고객은 제한 (공식 사이트 FAQ상 알뜰폰 중 KB리브엠은 예외) 지원 국가·언어의 iPhone 사용자. 1명과 통화할 때만 녹음 가능 지원 OS·기기 Android 10 이상, iOS 16 이상 iOS 17 이상 iPhone 12 이상 / Android...

타입캐스트 vs 클로바더빙: 수익 나는 채널에 쓸 때 무료·유료 조건 비교

요약 타입캐스트와 클로바더빙은 둘 다 글만 입력하면 한국어 AI 목소리를 만들어 주는 서비스지만, 무료로 쓸 수 있는 범위가 꽤 다릅니다. 클로바더빙 무료는 매달 15,000자까지 쓸 수 있는 대신 수익이 생기는 채널에는 쓸 수 없고, 타입캐스트 무료는 처음에 주는 약 5분 분량의 다운로드로 끝나는 체험판에 가깝습니다. 광고 수익이 붙은 유튜브나 쇼핑몰 영상에 넣을 목소리라면 처음부터 유료 플랜 조건을 보고 고르는 편이 안전합니다. 왜 이 두 서비스를 같이 비교하나 쇼츠 내레이션, 수업 자료 더빙, 상품 소개 영상처럼 "내 목소리 대신 AI 목소리"가 필요할 때 한국 사용자들이 가장 많이 찾는 곳이 네오사피엔스의 타입캐스트 와 네이버의 클로바더빙 입니다. 기능 소개만 보면 비슷해 보이지만, 실제로 문제가 되는 건 음질보다 "이 목소리를 내 채널에 써도 되나" 입니다. 그래서 이 글은 기능 나열보다 무료 사용 범위, 출처 표기 의무, 유료 플랜 가격과 다운로드 한도를 중심으로 정리했습니다. 모든 수치는 2026년 10월 25일에 두 서비스의 공식 요금 페이지와 고객센터 도움말에서 직접 다시 확인한 내용입니다. 한눈에 보는 비교표 항목 타입캐스트 무료 타입캐스트 베이직 클로바더빙 Free 클로바더빙 Standard 월 요금 0원 9,900원 (연간 결제 시 10% 할인) 0원 19,900원 (네이버 클라우드 플랫폼에서 결제) 무료·포함 사용량 음성 생성·재생 무제한, 다운로드는 최초 3,000크레딧(약 5분) 1회 지급 월 30,000크레딧(약 60분) 월 15,000자, 다운로드 월 20회, 프로젝트 누적 5개 (매월 1일 갱신) 월 30,000자, 다운로드 월 40회, 프로젝트 누적 20개 쓸 수 있...