Feature Request: Separate Billing/Usage Scope for Personal vs Business Copilot on Single Account #180313
Replies: 1 comment
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
General
Copilot Feature Area
Account Related
Body
I am currently in a situation where I have both a personal GitHub Copilot Pro subscription (for my own projects/agent usage) and a Copilot Business seat provided by my employer.
Currently, there seems to be no mechanism to separate the usage or billing between these two contexts on a single GitHub identity.
When a Business seat is assigned, it CANCELS the personal subscription. I cannot utilize a personal allowance of "Premium Requests" when working on personal projects. All usage is attributed to the business organization (costing them money/quota) or blocked if the organization has stricter policies than my personal plan would have.
Also, when creating Pull Requests with automatic Copilot Code Reviews, the cost/usage seems to be attributed ambiguously. If a PR is created in an Organization's repository, the Code Review usage should strictly be billed to that Organization, not against a user's personal limits.
To resolve this, users are being told to create secondary GitHub accounts solely for work and link it to VS Code Copilot extension. This contradicts GitHub's long-standing recommendation to maintain a single identity (
One account for work and personal) and creates significant friction.I am not alone in facing this; the community has been discussing the inability to segment usage effectively. See this Reddit thread.
Proposed Solution
Please introduce a "Billing Scope" or "Usage Context" selector within the IDE (VS Code/JetBrains) or the GitHub Copilot extension or even better: use Context-Aware Billing: automatically respect the repository context (e.g., if I am in a repo owned by
MyCompany, bill to Business; if inMyPersonalRepo, bill to Personal).Questions
Beta Was this translation helpful? Give feedback.
All reactions