[Feature Request] Chrome extension account selector decoupled from browser login

Status Closed — duplicate
Reported on v2.1.179
Maintainer reply None cached
Activity 3 comments · opened Jun 17, 2026 · closed Jun 21, 2026

Bug Description
Claude in Chrome extension has no account selector. It inherits the claude.ai login from the Chrome profile instead of letting me sign into a specific Claude account, so it can't match my Claude Code CLI account (sung@ardenly.com) when my Chrome is signed into a different account. The extension shows "connected" but uses the wrong account, and tabs_context_mcp fails with No group with id / No MCP tab group exists because the extension and CLI never bind to the same account. Workaround is a separate Chrome profile signed into the CLI account — but please add an in-extension account selector (decoupled from the browser's claude.ai session) so the integration can target a chosen Claude account directly.

Environment Info

  • Platform: darwin
  • Terminal: WarpTerminal
  • Version: 2.1.179
  • Feedback ID: 8d9f190c-17ee-4c2e-be45-5a11d8a74792

Errors

[]

View original on GitHub ↗

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