Potential bug in Visual Studio causing rate limiting

[cyconx]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

I asked Copilot to analyse my Copilot Logs. It discovered a few problems which might help explain part of my rate limiting problems.

Have any of you got similar problems?

I have restarted VS and PC, Repaired VS, Uninstalled VS, reinstalled VS, Run virus check, etc.

Here’s a clean breakdown analysis of my logs.

---

✅ What looks good

1. Authentication is stable

2. Requests are actually going through

---

⚠️ What looks wrong / concerning

1. Severe request duplication

This line is everywhere:

Request augmented by responder callback. Previous request content:

Often repeated 5–8 times for the same prompt.

That almost certainly means:

• The prompt is being re-hydrated and resent
• Or multiple responders / middleware hooks are firing
• Or Copilot Chat UI is re-issuing the same logical request

👉 This causes:

• High latency
• Token churn
• Perceived “Copilot doesn’t respond / responds late”

This matches your real‑world experience very closely.

---

2. UI.SessionViewModel warnings

Repeated warning:

[UI.SessionViewModel Warning] DualResponseViewModel or control request is null.

This points to:

• A UI state machine bug
• A dropped or partially-initialized response stream
• Likely related to the duplication above

✅ Auth is fine
❌ UI orchestration is not

---

3. Excessive background token checks

You are seeing identity refreshes roughly every 25 minutes, which is correct — but the number of times identity is fetched is excessive.

This pattern:

Getting Copilot identity from service.
VsHttpClientFactory...
Status Code: 200

…appears far more often than necessary.

Likely cause:

• Every duplicated request path re-checks identity
• No effective memoization / reuse of valid token

---

4. High “Loaded 3 skills” churn

[Conversations] Loaded 3 skills.

This should be fairly static per session, but it’s repeating constantly.

That suggests:

• Session context is being rebuilt repeatedly
• Or session lifetime is shorter than intended

---

✅ Net assessment

Severity: 🟡 Functional but inefficient
Root cause area: Client-side Copilot Chat orchestration
Not the cause: Auth, token expiry, account status, subscription

Area	Status
Auth	✅ Solid
Token validity	✅ Correct
Request delivery	✅ Works
UI state handling	❌ Buggy
Request deduplication	❌ Broken
Performance	❌ Degraded

---

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