Inconsitent AI credit values between fork sessions and established limits #210402
Unanswered
fmigneault
asked this question in
Copilot Conversations
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. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Bug
💬 Feature/Topic Area
Copilot in GitHub
Body
When using a
/forksession with a/limitsconfigured, the model / harnest seems really confused about the values. It reports the previously set limit of1000, and a ratio of it applied within the current fork. However, trying to increase its limit to e.g.1200so it can resume work reports the AI credit values employed in the combined/original session.This makes it very odd for a user to set correct limits since we don't really have a clear idea of what was already included in the original session vs only the new portion from the fork (as indicated by the
(partial)). Because in this case I have to set something like3000relative to the overall value, I have no guarantee that the harness might not suddenly start to consider920.75 / 3000, which is much more than the few extra AI credits I want to allow.All reactions