Skip to content

[FEATURE]: Use more than one GitHub Copilot account side by side (github.com + GitHub Enterprise) #53376

Closed as not planned

Description

@MrDix

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

I work for customers who each provide their own GitHub Copilot licence - some on github.com, some on their own GitHub Enterprise (ghe.com) instance - next to my employer's account. In 1.18.x Copilot always uses the provider ID github-copilot, and auth.json keeps one entry per provider, so logging in to a second account replaces the first.

Related, but not the same: #5391 was closed with a pointer to v2, and #51152 asks for per-project credential activation in v2. This request is for the 1.x line, and for using the accounts side by side rather than switching between them: models of both accounts in the picker, and a project pinned to one account through disabled_providers or model.

Proposal, without new config schema: every configured provider whose ID starts with github-copilot- is an additional Copilot account. It gets its own login (the usual device flow, against options.enterpriseUrl if set - that option is in the schema but unused today), its own credentials and its own model list, reusing the existing Copilot plugin, the models.dev catalog entry and the Copilot model routing.

"provider": {
  "github-copilot-acme": {
    "name": "GitHub Copilot (ACME)",
    "options": { "enterpriseUrl": "acme.ghe.com" }
  }
}

I have this working on 1.18.x (Copilot plugin, plugin registration and provider.ts, with tests and a docs section) and would open a PR if it fits. Or is multiple accounts strictly a v2 topic?

Activity

  1. github-actions commented on Oct 5, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of or overlap with existing issues. Please check:

    • #2350: asks about logging in to multiple GitHub Copilot accounts.
    • #20423: requests named profiles for multiple GitHub Copilot accounts (personal and work).
    • #25738: proposes multiple credentials per provider, explicitly including GitHub Copilot.
    • #5391: requests multiple auth profiles per provider.
    • #6217: requests multiple named instances of the same provider in the model picker.
    • #51152: overlaps the project-specific credential selection aspect (focused on v2).
  2. jakoss commented on Oct 10, 2026

    @jakoss

    The multiple provider support is only on v2 and v1 seems to be closed for contributions since today. I doubt this will move forward

  3. opencodejr commented on Oct 27, 2026

    @opencodejr

    Thanks for the detailed proposal and for offering a PR, @MrDix!

    The 1.x line (opencode-ai) now only gets fixes for critical bugs such as data loss, security problems or breakage with no workaround. New features like multiple Copilot accounts are unlikely to land there, so a 1.x PR for this probably won't be merged.

    Multiple accounts are a v2 topic (@opencode/cli, opencode command). v2 can already store several credentials per integration, with one active at a time. Choosing the account per project or per session is being discussed here:

    If you can, please try v2 and add your github.com + GHE use case to #51152. Your experience there, including having the models of both accounts in the picker at the same time, would be valuable input. If you think this is critical for 1.x, or you run into the same limitation on v2, please reply here.

  4. opencodejr commented on Oct 28, 2026

    @opencodejr

    Closing this as not planned. Multiple GitHub Copilot accounts side by side is a feature request for the 1.x line, which now only gets critical fixes, and we haven't heard back since the last comment.

    The multi-account work is happening in v2. Please add your github.com + GHE use case to #51152 (per-project account selection) or #54136 (per-session selection). If you run into this limitation on v2 too, or think it's critical for 1.x, feel free to comment here or open a new issue. Thanks again for the detailed proposal!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions