The #1 reason my company won't use Github Copilot right now

[hades200082]

Select Topic Area

Product Feedback

Copilot Feature Area

Copilot Enterprise

Body

The #1 reason my company won’t use GitHub Copilot right now

We already use Claude Code successfully. We also already use GitHub for all company repositories, and - exactly as GitHub has encouraged for years - our developers use a single GitHub account for both work and personal repositories. Some of them already pay for individual Copilot for side projects.

So adopting GitHub Copilot should be easy.

It isn’t, because of one policy:

When our company assigns a Copilot seat to a developer, GitHub automatically cancels their individual Copilot subscription on that same account.

That forces an uncomfortable outcome: developers who want to keep using Copilot on personal projects are pushed to use a company-paid Copilot seat outside company work (or to create awkward workarounds like maintaining a second GitHub account).

Why this is a blocker (and not just a billing issue)

Many employment contracts and company policies, ours included, treat “company resources/tools” as a factor in IP ownership and disclosure obligations. Even if no one intends to claim anyone’s side project, GitHub’s policy creates avoidable ambiguity:

• A developer loses their personal subscription involuntarily.
• The only way to keep using Copilot personally is to use the company-provided seat (or stop using Copilot personally).
• Now personal work is entangled with company-provided tooling—exactly the situation many developers work hard to avoid.

This is why we can’t responsibly roll Copilot out right now.

The frustrating part: GitHub already has enough context to solve this cleanly

For the Copilot VS Code extension and Copilot CLI, GitHub could separate personal vs company usage without forcing subscription cancellation. Two straightforward approaches:

1) Auto-detect based on repo context (best default)

In most real workflows, you’re in a folder that is either:

• a git repository, and/or
• already connected to a GitHub remote, and/or
• associated with an organization via the remote URL

Copilot can use that context to select the right “billing identity” automatically:

• Org remote / org-owned repo → use org seat
• Personal repo → use personal subscription
• No remote yet → fall back to asking the user (see below)

2) When there is no repo yet, just ask the user (simple, explicit)

A lot of work starts before the first commit or remote exists: prototypes, new projects, scratchpads.

In those cases, the CLI/extension should simply prompt:

“Which Copilot license should be used for this workspace?”

• Personal
• Company (Org: X)
• Company (Org: Y)

This one prompt eliminates ambiguity and creates a clear user-controlled boundary. It should also be visible in the UI (“Copilot: Personal” vs “Copilot: Company”) so users don’t make mistakes.

This is not an edge case - lots of people are raising the same issue

Here are just a few of the existing community threads:

• https://github.com/orgs/community/discussions/56234
• https://github.com/orgs/community/discussions/111258
• https://github.com/orgs/community/discussions/162273
• https://github.com/orgs/community/discussions/171377
• https://github.com/orgs/community/discussions/152915

What we’re asking GitHub to change

At minimum:

• Stop auto-canceling individual Copilot subscriptions when an org seat is assigned.

Better:

• Allow personal + org Copilot to coexist on one GitHub account, and
• Select the correct license per workspace using repo detection, and ask the user when it’s ambiguous.

Bottom line

We want to like Copilot. We already live on GitHub. But GitHub’s current licensing behavior turns a normal “assign a seat” action into a personal-vs-company IP boundary problem.

GitHub can fix this with straightforward product behavior in the Copilot VS Code extension and Copilot CLI: auto-detect when possible, and ask the user when not.

Until then, we’ll stick with what we have.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐