Copilot (web) does not return result. But still cost credits.

[tjuxxc]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

1. In a long conversation, copilot keeps thinking for hours, but returns no result. The model is Claude opus 5.
2. In another short (almost new) conversation, copilot keeps searching files for at least an hour, but returns no result and costs credits! The model is Claude opus 5.5.
   I have Copilot Pro+ subscription.

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

[4Raisan]

Since this happens in both a long conversation and a nearly new one, conversation length alone does not explain the report. I would stop the stuck request rather than leave it searching indefinitely, and avoid repeatedly resubmitting the same expensive request.

For one controlled comparison, use a fresh chat, select a different model that is currently available in your picker, and ask a narrowly scoped question about one specified file instead of a repository-wide search. If that succeeds, the evidence points toward the original model/session or its search path; if it also hangs, test the same small request without repository context to separate basic chat from repository retrieval. These are diagnostic comparisons, not a confirmed fix.

Before closing the affected sessions, record their URLs, UTC start times, selected models and the relevant usage entries. Send those through https://support.github.com/contact and explicitly mention that the request never returned an answer while usage increased. Only Support can inspect the account-side request and billing records or determine whether an adjustment is appropriate. Don’t post private repository contents, tokens or unsanitized browser network exports here.