[Labelling Correction Signal] Discussion #160: GitHub Copilot Token stuck in infinite "Computing/Processing" state (Server-side lock…

[mnkiefer]

This issue records trusted label corrections for one discussion. It is a deterministic intake record for later agentic analysis of .github/instructions/community-discussion-labeling.md.

Signal key: githubnext/aw-community-discussions#160
Discussion number: 160
Target repository: githubnext/aw-community-discussions
Discussion URL: https://github.com/githubnext/aw-community-discussions/discussions/160
Current category: Copilot Conversations
Current category slug: copilot-conversations
Current labels: bug, Copilot, Copilot in GitHub
Seen labels: Copilot
Seen event types: labeled
Correction count: 1
First correction seen: 2026-04-13T21:06:54.486Z
Last correction seen: 2026-04-13T21:06:54.486Z
Latest event type: labeled
Latest label: Copilot

Discussion Snapshot

Title: GitHub Copilot Token stuck in infinite "Computing/Processing" state (Server-side lock suspected)

🏷️ Discussion Type Bug 💬 Feature/Topic Area Copilot in GitHub Body I've already tried signing out, clearing local cache, and reinstalling the extension, but Copilot is still stuck in a perpetual "computing" state. It seems like a server-side session deadlock associated with my account. Can you please manually reset or clear my Copilot backend session/token state? Thanks.

Correction History

When	Event	Label
2026-04-13T21:06:54.486Z	labeled	Copilot