-
Notifications
You must be signed in to change notification settings - Fork 7.2k
Description
Preflight Checklist
- I have searched existing requests and this feature hasn't been requested yet
- This is a single feature request (not multiple features)
Problem Statement
Note: This is just a duplicate of Issue #15581 which was closed due to inactivity. The github-actions bot suggests we open a new issue if this is still relevant.
As mentioned in another comment, this a more general issue:
This applies to all connectors, not just GitHub. Can't have multiple Gmail connected at the same time, which forces separate subscriptions. Profile-scoped connectors would solve it.
Currently, Claude Code on the web (claude.ai/code) only allows connecting a single GitHub account through the Connectors settings (Settings → Connectors → GitHub).
As a developer, I maintain multiple GitHub accounts:
- Personal account for side projects
-
- Work/organization account for professional work
When I connect my personal GitHub account, I cannot access repositories from my work account, and vice versa. The only workaround is to disconnect and reconnect with a different GitHub account each time, which is cumbersome and disrupts workflow.
- Work/organization account for professional work
Note: Issue #261 addressed multiple accounts for the CLI version using CLAUDE_CONFIG_DIR environment variable, but this solution doesn't apply to the web interface (claude.ai/code).
Proposed Solution
Allow users to connect multiple GitHub accounts in Claude.ai Settings → Connectors, similar to how other development tools (VS Code, JetBrains IDEs) handle multiple accounts.
Ideal implementation:
- Add ability to connect additional GitHub accounts in Connectors settings
- Show repositories from all connected accounts in the repository selector dropdown
- Clearly indicate which account each repository belongs to in the UI (e.g., "username/repo-name")
- Allow users to set a default account or choose per-session
Alternative Solutions
No response
Priority
Medium - Would be very helpful
Feature Category
MCP server integration
Use Case Example
No response
Additional Context
No response