User-level AI Credits budget not tracking consumed_amount — prevent_further_usage never triggers for values > $0

[amartingarcia]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot Enterprise

Body

Summary

I configured a user-level AI Credits budget at enterprise level with
prevent_further_usage: true and a limit of $1. The budget never blocks
usage because consumed_amount stays at 0.0 regardless of actual consumption.

A $0 budget does block correctly — so the field is read somewhere, but the
pipeline that updates consumed_amount appears broken for any value > $0.

Environment

• GitHub Enterprise Cloud
• Mix of Copilot Business + Copilot Enterprise seats
• Budget created after June 1, 2026 (usage-based billing launch)

Steps to Reproduce

1. At enterprise level, create a user-level AI Credits budget:
   • Amount: $1
   • Scope: specific user (or universal)
   • "Stop usage when budget limit is reached": enabled
2. Use Copilot Chat with any premium model (e.g. Claude Sonnet, GPT-4o)
   across several sessions — enough to clearly exceed $1 in AI credits
3. Verify real consumption in the AI usage dashboard
4. Check the budget via REST API:

   GET /enterprises/{slug}/settings/billing/budgets
   

Expected Behavior

consumed_amount reflects real usage. Once it reaches the configured
budget_amount, prevent_further_usage: true blocks further access.

Actual Behavior

consumed_amount remains 0.0. Copilot continues working with no
interruption regardless of how much is consumed.

API Response (sanitized)

{
  "budget_type": "BundlePricing",
  "budget_product_sku": "ai_credits",
  "budget_scope": "user",
  "budget_amount": 1,
  "prevent_further_usage": true,
  "consumed_amount": 0.0
}

Key Observations

• $0 budget works: setting budget_amount: 0 blocks the user immediately
  (different enforcement path — static rule, no counter needed)
• $1+ budget never blocks: consumed_amount never increments, so the
  threshold is never reached
• Budget is correctly created with budget_product_sku: "ai_credits"
  (not the legacy premium_requests)
• Budget is visible in the API response and correctly shows
  prevent_further_usage: true

Related Discussions

• Cannot see/edit AI credits budget with user scope #197601 — ULBs not visible in org UI (different issue, UI/filter bug)
• All users in Copilot Business are blocked due to “budget limit reached”, but AI credits usage is far below limit #197549 — Users blocked despite usage below limit (opposite symptom)

This is distinct from both: the budget exists, is correctly typed, and is
reachable via API — but the consumption counter simply never updates.

Impact

With consumed_amount stuck at 0.0, there is no effective per-user
enforcement for any value > $0. The only working option is $0 (full block),
with no granularity in between.

[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. ⭐