Memory: No billing entity selected #202462
Replies: 3 comments
|
Even if your personal account is the only available option, you must explicitly select it so the system can map your user preferences to a billable owner. GitHub Copilot operates on an AI Credits system, where 1 AI credit equals $0.01 USD. What remains unlimited: Standard inline code completions and next-edit suggestions are still completely unlimited for your paid plan and do not consume credits. What consumes credits: Copilot Chat, CLI, and Agent sessions are billed based on the tokens they consume (both input and output). When Copilot creates context for a session, it looks at your active billing entity, retrieves your stored memories, and includes them in the prompt. The tokens consumed by injecting those memories into the AI model are billed to your account. **Because agent mode and chat can consume tokens quickly, there is no automatic spending limit applied by default. To protect yourself from surprise overages, it is highly recommended to go to Settings > Billing > GitHub Copilot and set a manual monthly spending cap. Once your personal account is mapped, Copilot Memory will quietly run in the background, deleting unused facts automatically after 28 days to keep your context fresh.** |
|
I am seeing the same issue with Copilot CLI 1.0.73. Copilot Memory is enabled, but the documented settings page only shows the Memory preview toggle and a Manage billing link. There is no billing entity selector, so I cannot explicitly select an entity even though |
|
Hi, @rflulling! Based on your description, this doesn't seem to be a configuration issue on your end. Since you only have a personal account with GitHub Pro and Copilot Pro, but there's no option to select a default billing entity, it seems the UI isn't matching the documentation. I also noticed that another user in this discussion reported the same error. That makes it seem more likely that this is a GitHub-side issue rather than something specific to your account. I'd recommend signing out and back in once to refresh your account state. If the billing entity selector still doesn't appear, it's probably best to open a GitHub Support ticket and include screenshots of the missing selector along with the exact error message. That should help the support team investigate the issue further. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Profile, Billing, Features
Body
I have gone to several links separately specified as solution destination. None have an option or any sort of notice that even resembles the issues named. My account embodies the top most line below. Following that are excerpts from the about page.
I thought this previous service was enabled by default and according to the about page it is. But my account tell me different. Billing is needed. But there is nothing under billing that exists in a undefined state or on multiple states. Additional information is needed. Also if this is a billed service I need additional information and clarity on how that works.
Storage of repository facts and user preferences will fail if no billing entity is selected. Manage billing.
Copilot Business and Copilot Enterprise plans
On Copilot Business and Copilot Enterprise plans, user-level preferences can also be exported or deleted by an organization or enterprise administrator, either in bulk or per user.
Preferences are owned by the billing entity, which is the organization or enterprise that grants the user their license. When a memory is created, it is stored against the active billing entity for the user's current usage. Then, when Copilot creates context for an agent session, it looks at the user's current active billing entity again and only retrieves memories that are owned by that billing entity. Users can view all their stored preferences and corresponding owners in their personal settings.
Users who have multiple licenses from different places must select a default billing entity in their account settings in order to generate user-level preferences.
Retention and validation
To prevent stale information from lingering, any stored fact or preference that goes unused is automatically deleted after 28 days. The 28-day timer may reset whenever Copilot successfully validates and uses an entry.
Facts can also be captured from pull requests that were closed without merging. In those cases, the validation step ensures that Copilot's behavior is unaffected unless the current codebase still substantiates the information.
Enabling Copilot Memory
Copilot Memory is enabled per user, not per repository. Once enabled, it applies in any repository where that user works with GitHub Copilot. For individual plans, it's on by default. For enterprise- and organization-managed plans, an administrator must enable the policy first, and then individual users can opt out.
For more information, see Managing Copilot Memory for your personal account or Managing Copilot Memory for an organization or enterprise.
All reactions