[BUG] Authentication succeeds but Claude Code doesn't respond - "Auth Token: none" despite successful login (v2.0.14, macOS)

Status Closed — not planned
Maintainer reply None cached
Activity 8 comments · opened Oct 11, 2025 · closed Feb 5, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

After successfully completing the OAuth login flow using my Claude Max subscription, Claude Code shows "Login successful" but immediately becomes unusable. The authentication token is not persisted - /status shows "Auth token: none" and Claude Code doesn't respond to any prompts. Every attempt to use Claude Code results in "Missing API key · Run /login" error, making it completely unusable despite having an active paid subscription.

What Should Happen?

After successful OAuth authentication with Claude Max subscription, Claude Code should:

Store and persist the authentication token in the system keychain/config
Display the auth token status (not "Auth token: none")
Respond normally to all user prompts without asking to re-login
Function as expected for a paid subscriber

Error Messages/Logs

Steps to Reproduce

Missing API key · Run /login

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

v2.0.8

Claude Code Version

2.0.14

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

8 Comments

github-actions[bot] · 1 year ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/5244
  2. https://github.com/anthropics/claude-code/issues/5166
  3. https://github.com/anthropics/claude-code/issues/8002

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

timyal · 1 year ago

In that terminal where Claude just started, first exit:
exit

Then run these commands in sequence:

Step 1: Unlock keychain
security unlock-keychain ~/Library/Keychains/login.keychain-db

(Enter your Mac password when prompted)

Step 2: Start Claude
claude

Then in the Claude session:
/login

Wait for "Login successful" (even though it will still show "Missing API key")

exit

Step 3: Start Claude again
claude

Julianlaue · 10 months ago

I am having the same issue

github-actions[bot] · 9 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

edronen · 9 months ago

I was having the same issue when running Ubuntu, which is running on my proxmox home lab. Yes, different environments, but because it took me hours to figure it out, I'm hoping this can also help others.

The documentation file is just explanation of what was happening to me, but more importantly the claude-oath-fix.sh script is what I was able to use to get my token to persist and finally start using it again. HTH!

claude_oauth_fix.sh
CLAUDE_CODE_OAUTH_FIX_DOCUMENTATION.md

github-actions[bot] · 8 months ago

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

marcindulak · 8 months ago

This issue was closed incorrectly despite recent human comments. This behavior of the bot is reported at https://github.com/anthropics/claude-code/issues/16497. Please upvote that issue, so maybe it gets noticed.

github-actions[bot] · 8 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.