Copilot should not consume Premium Requests when sessions fail #195549
Replies: 2 comments
-
|
💬 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.
-
|
It happened to me too. A Copilot Agent session failed without giving a clear reason or any usable output, but it still appeared to consume Premium Requests. I understand that Copilot Agent sessions may count as Premium Requests once a session starts, but this behavior is confusing when the session fails before producing a meaningful result. From the user’s side, it feels like quota is being charged even though no successful service was delivered. At minimum, GitHub should show a clear per-session usage record with:
If a session fails silently or produces no usable result, it should either not consume Premium Requests or the consumed requests should be automatically credited back. This would make Copilot Agent billing much more transparent and fair. |
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.
-
Copilot Agent sessions should not consume Premium Requests when the session fails with no reason or no usable output
Issue
GitHub Copilot Agent sessions appear to consume Premium Requests even when the agent session fails without providing a clear reason, diagnostic explanation, or usable result.
This is a billing and transparency problem.
If the agent fails before delivering a usable output, the session should not be counted as a successful Premium Request consumption event.
Expected behavior
When a Copilot Agent session fails with:
then the session should not consume Premium Requests.
Alternatively, GitHub should automatically refund or credit the consumed Premium Requests.
Actual behavior
The user may lose Premium Requests even though the Copilot Agent session produced no usable result and failed without explaining why.
From the user’s perspective, this means quota or billable usage is consumed for a failed service delivery.
Why this matters
Premium Requests are a limited and potentially billable resource.
An agent session that fails silently or without a clear reason should not be economically equivalent to a successful Copilot Agent execution.
This is especially important for Copilot Agent workflows because they can consume multiple Premium Requests during a session. If the session fails, the user needs to know:
Requested clarification
Please clarify:
Proposed rule
Copilot Agent Premium Requests should only be consumed when the session produces usable output or completes a meaningful step.
If the agent session fails with no reason, no result, or no user-visible diagnostic, the Premium Requests should not be consumed.e delivery. Failed sessions should not silently consume a scarce or billable resource without clear disclosure.
Beta Was this translation helpful? Give feedback.
All reactions