[BUG] Code tab forces enterprise AWS SSO on personal Pro account, ignores existing app session
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?
Description
The Chat tab and Code tab in the Claude desktop app use completely separate authentication flows. The Chat tab correctly uses my personal Gmail session. The Code tab ignores that session entirely and triggers a new auth flow that detects ~/.aws/config, finds the corporate AWS SSO endpoint, and forces enterprise authentication with no option to choose a different account or go back.
What Should Happen?
Expected Behavior
The Code tab should use the account session already authenticated in the app, or provide an account selection step before initiating SSO.
Actual Behavior
Code tab reads ~/.aws/config independently, detects corporate SSO, and forces enterprise auth with no override possible. CLAUDE_CONFIG_DIR has no effect on the Code tab auth flow.
Error Messages/Logs
Steps to Reproduce
- Have ~/.aws/config configured with a corporate AWS SSO profile
- Log into Claude desktop app with a personal Gmail account
- Open the Code tab
- Observe immediate redirect to enterprise AWS SSO with no account selection step and no way back
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.89 (Claude Code)
Platform
AWS Bedrock
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
What I Tried
- CLAUDE_CONFIG_DIR via
launchctl setenv - CLAUDE_CONFIG_DIR via
~/.config/claude/env - CLAUDE_CONFIG_DIR injected at launch:
CLAUDE_CONFIG_DIR="$HOME/.claude-personal" open -a "Claude" - All confirmed that the Code tab ignores CLAUDE_CONFIG_DIR entirely
Impact
Users with both a personal Claude Pro subscription and a corporate Claude enterprise account on the same machine cannot use the Code tab with their personal account at all. The Chat tab and Code tab behave as entirely separate products with no shared session context.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗