[BUG] Login flow for VS code extension fails

[ArnimJ]

Preflight Checklist

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

What's Wrong?

When I try to login using my API key in VS code, the login flow works as expected but the actual login fails at the end. Both the manual and browser auth fails. It just shows the same login options again and doesn't work.

What Should Happen?

login should work once you auth in the browser or paste the code manual. both options fail.

Error Messages/Logs

Steps to Reproduce

1. try to login
2. click anthropic console option
3. auth in the browser which works fine. login successfully, get kicked back to vs code
4. Try putting in a prompt
5. Prompted to login again

Trying the manual approach leads to a blank screen after you paste the code.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.63

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] VS Code extension 2.0.5.0: Invalid API key · Please run /login and black screen even after successful Anthropic Console OAuth and manual API key setup #12204
2. [BUG] Failed to retrieve auth status after login. #28074
3. [BUG] API key authentication accepts credentials at login but fails on first message (Debian/Linux) #28176

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

[github-actions]

This issue has been automatically closed as a duplicate of #12204.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[github-actions]

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.