Reqest for Credits.....

[david3272]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot Agent Mode

Body

I experienced repeated failed iterations and packaging/runtime errors during a Copilot CLI-assisted workflow, resulting in significant extra usage and time cost.
Please review this session for courtesy credit consideration.
Key issues included repeated ZIP path separator incompatibilities on Linux (\ vs /), activation fatals, and multiple rework cycles before stable artifacts were produced.
Requesting complimentary credits for this session due to avoidable tool-assisted rework overhead.

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

[xusnitdinov]

@david3272 community folks can't issue Copilot / usage credits from a Discussion. That has to go through GitHub billing/support.

Best shot:

1. Open https://support.github.com/ and pick the Copilot / billing path
2. Include the session/time range, that it was Copilot CLI, and the failure pattern (ZIP \ vs / on Linux, activation fatals, rework loops)
3. Ask for a courtesy credit review. Be short and factual.

Discussions are good for product feedback about the CLI bugs themselves. Credit refunds only happen if Support/billing decides to grant them.