[BUG] No logout mechanism in VSCodium extension — credentials irrecoverable without CLI

Resolved 💬 3 comments Opened May 29, 2026 by SlyPhi Closed Jul 2, 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?

The Claude Code extension for VSCodium (Linux) has no logout button, no account switcher, and no documented credential storage location. This creates an unrecoverable loop when the wrong account is authenticated:

Extension stores credentials in an undocumented location — not in ~/.claude/.credentials.json, not in ~/.config/VSCodium/User/globalStorage/, not in the system keyring (verified via seahorse and secret-tool)

The only logout mechanism is claude logout via the CLI

claude logout redirects to browser and requires an active subscription to complete — if the authenticated account has no subscription, the command fails and returns an "upgrade" prompt

Result: completely irrecoverable state without Anthropic support intervention

What Should Happen?

A logout button in the extension UI, or at minimum documented credential storage so users can manually clear state.

Error Messages/Logs

Steps to Reproduce

1 Install Claude Code extension in VSCodium on Linux
2 Authenticate with an account that has no Pro subscription
3 Attempt to log out or switch accounts
4 Observe there is no mechanism to do so

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

claude --version Credit balance is too low

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

Additional issues surfaced by this bug:

  • Payment flow does not capture or confirm email address, making wrong-account purchases trivially easy
  • No in-extension account status or logout option despite this being standard practice for any authenticated extension

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗