Authentication issues on VS Code — page 2
Issues the maintainers labelled both platform:vscode and area:auth.
141 issues · 43 open · 98 resolved (70%) · first seen Feb 24, 2026
Is this getting better or worse?
This class of problem is holding steady. 44 new reports in the last 90 days vs 53 in the 90 before — -17%. The open backlog peaked at 43 in 2026-10 and sits at 43 today.
Derived by counting each matching issue from its creation date until it closed. First-party
computation over the anthropics/claude-code tracker — the trend is not published
anywhere upstream.
Which builds report this
104 of these reports name the Claude Code build they were running, spanning 71 releases. Heaviest reporters:
- Claude Code v2.1.296
- Claude Code v2.1.280
- Claude Code v2.1.241
- Claude Code v2.1.150
- Claude Code v2.1.76
- Claude Code v2.1.114
- Claude Code v2.1.286
- Claude Code v2.1.251
Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.
Do these get fixed?
Median time to close is 32 days across 98 closures. Of the 98 closures with a recorded reason, 24% were closed as completed and 74 as not-planned or duplicate. The most recent completed fix landed in 2026-09.
Workarounds reported by the community
35 of these issues post a workaround someone says worked. The highest-engagement ones:
- [BUG] API Error: Rate limit reached despite Claude Max subscription and only 16% usage
- …nType: null and rateLimitTier: null. API credits were added as a workaround — they were consumed instantly (within seconds), leaving the account in debt. After fresh login subscription is recognized (subscriptionType: "m…
Found in the description of #29579 · still open - [FEATURE] Multi-account support in VSCode extension
- …quota of a single Claude Pro account within a day. A common workaround is to maintain two separate Claude Pro accounts and switch between them. This works well in the terminal via , but the VSCode extension always uses a…
Found in the description of #55621 · still open - [BUG] Cannot paste auth code into "Paste code here if prompted >" during /login in Dev Container (v2.1.105)
- I have a solution that works for me. WSL workaround when paste is broken during /login If you're on WSL, have no browser, and can't paste the token, install wslu so WSL can open your Windows browser for the OAuth flow: R…
Found in the thread of #47699 · resolved - [BUG] "Remote Control environments are not available for your account." for Claude Code Pro Plan user
- …lly will fix this — it's server-side. Stop spending time on workarounds. 2. 👍 vote on the upstream tracking issue 28817 to signal demand for faster Pro rollout 3. Upgrade to Max plan ($100/month) if Remote Control is cr…
Found in the thread of #29449 · still open - [BUG] Extension 2.1.207 breaks Bedrock SSO auth (UnauthorizedException: Session token not found or invalid) — 2.1.206 works
- …ARN. - Settings follow the documented SSO pattern exactly: Workaround Bypass the bundled SSO resolver and hand Claude Code materialized credentials from the AWS CLI: With this set, requests succeed again.
Found in the thread of #77138 · resolved
Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.
Matching issues 101–141
Ranked by community engagement (reactions weighted over comments).
- [Bug] Paid Claude Max subscription not visible on claude.ai web despite active CLI authentication
- [BUG] Server outage caused immediate and total lockout of Claude Code in VS Code
- [BUG] Personal account organization name not updated after changing display name in claude.ai
- [BUG] Claude VSCode extension: on every update I need to re-authenticate
- [Bug] VSCode Extension: Token Exchange Failed with HTTP 400 Status
- [BUG] Claude VSCode Extension loses Authorization Info
- [BUG] VS Code extension login prompt not bypassed with claudeCode.disableLoginPrompt: true when using Microsoft Foundry
- [BUG] API key authentication accepts credentials at login but fails on first message (Debian/Linux)
- [BUG] Forced re-authentication mid-session leaves the Artifact tool "switched off" for the rest of the session (same account)
- [BUG] Sessions list view crashes with TypeError in getAuthStatus when stored auth state is malformed
- [BUG] VSCode extension's /mcp OAuth flow ignores configured --callback-port (uses a different port than the terminal CLI)
- [BUG]
- [BUG] Won't let me sign in on VScode
- VS Code extension: in-app 'Log in' fails with 400 on claude_oauth_callback after refresh-token expiry
- I need more specific information about the error you're experiencing to generate an accurate issue title. Could you please provide: 1. The error message you're receiving 2. What MCP server you're trying to integrate 3. What steps you took to set it up 4.
- VS Code extension checks entitlements differently than Desktop — Apple-subscription Pro accounts see "Free" plan model access errors
- subscriptionType shows "pro" instead of "max" for Max 5x subscribers
- VS Code: session resume from claude.ai/code fails with lock contention and expired OAuth token
- [Bug] Opus 5.5 shows "This model requires a Pro plan" on Max plan
- [BUG] VS Code WSL authentication fails without actionable error when Windows and WSL have different effective internet connectivity
- MCP connector stuck on a false "Needs Auth" in VS Code; re-authorizing cannot clear it — only disabling and re-enabling the server in /mcp
- [BUG] claude.ai connectors silently missing for the whole session when the connector-list fetch gets a 401 at first launch of the day — 401 is never retried, even after the token refresh succeeds
- [FEATURE] VSCode Extension login is derived from base VSCode instance
- [BUG] VS CODE EXENSION IN WINDOWS LOGS ME OUT EVERY DAY. WHY WON'T YOU FIX THIS?
- [BUG] Claude apps gateway: CLI and VS Code sharing a session present a stale refresh token; IdP with rotating tokens revokes the chain and both clients are logged out
- [BUG] Remote Control fails with generic HTTP 403 when Trusted Devices is enabled (VS Code extension, Windows) instead of the "device not enrolled" error
- [BUG] VS Code extension: the re-login prompt on Send throws away the typed message; dictation fails with 'No OAuth token available for speech-to-text'
- Credit balance is too low
- System context not updating when switching Claude accounts
- [Feature Request] Allow API key storage in configuration file with user consent
- You've hit your session limit · resets 3:10pm (Asia/Makassar)
- [BUG] VS Code extension shows Pro, claude.ai shows Max.
- [BUG] Claude Code blocked on new personal Pro account - oauth_org_not_allowed
- Windows: VS Code panel shows 'OAuth session expired and could not be refreshed' although re-login succeeds (stale-process refresh race + resumed session re-renders old auth error)
- [Bug] Fable 5.1 incorrectly blocked by usage credits prompt on Claude Max plan
- Forced re-login wipes ~/.claude transcripts; concurrent instance deletes a live session's task output files (Windows)
- [BUG] Signing in to VS code returns a 400 error
- No way to reauthorize a claude.ai connector (e.g. Datadog) from within the VS Code extension
- [BUG] MCP server shows "Needs Auth" after VSCode restart despite valid token
- [Bug] Remote Control unavailable for non-organization MAX plan users
- [BUG] Claude Code VS Code extension resolves account to API org instead of active Pro subscription