Access denied Single sign-on to view this chat.

[aarsht7]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

I was working on some vibe code last Friday, and since I have turned off my PC, I am unable to retrieve this specific chat. I was using the Copilot web interface with Gemini 3.1 pro, not the VS Code extension. The issue is only with this specific chat. Other functions are working properly.

Things I tried can be found here.

#196191 (reply in thread)

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

[Pronoydebnath]

This sounds more like a corrupted or unsynced conversation state rather than a full Copilot outage, especially since:

• only one specific chat is affected,
• other Copilot features still work,
• and the issue started after shutting down/restarting your PC.

A few things you could try:

• Refresh the Copilot web page completely (Ctrl + F5)
• Log out of GitHub and log back in
• Try opening the chat from another browser or incognito/private mode
• Check whether the conversation still appears in your Copilot chat history/sidebar
• Disable browser extensions temporarily (ad blockers/privacy extensions can sometimes interfere)

If the chat opens but fails to load messages, there’s a chance the conversation metadata exists but the backend session became corrupted or expired.

Unfortunately, if the specific conversation was never fully synced server-side, it may not be recoverable from the web UI after the session ended.

Since this involves the Copilot web interface specifically (not VS Code), it may also help to mention:

• browser name/version,
• whether the chat shows an error message or infinite loading,
• and whether the issue happens across devices.

That would help others confirm whether it’s a reproducible Copilot web bug.

[aarsht7]

• Refresh the Copilot web page completely (Ctrl + F5)

• Did not work

• Log out of GitHub and log back in

• Did not work (tried it on 2 different PC with 2 different OS)

• Try opening the chat from another browser or incognito/private mode

• Did not work

• Check whether the conversation still appears in your Copilot chat history/sidebar

• Yes, that's how I am opening it for lending on the same error page

• Disable browser extensions temporarily (ad blockers/privacy extensions can sometimes interfere)

• Tried it with Brave and freshly installed Firefox

Since this involves the Copilot web interface specifically (not VS Code), it may also help to mention:

• browser name/version,

• Brave latest from Flathub (v 1.90.122), Firefox latest from Flathub (150.0.3)

• whether the chat shows an error message or infinite loading,

• error message on display/ console error below

• and whether the issue happens across devices.

• YES

chunk-EPOLDU6W.mjs:193 Matched leaf route at location "/copilot" does not have an element or Component. This means it will render an <Outlet /> with a null value by default resulting in an "empty" page.
ex @ chunk-EPOLDU6W.mjs:193
/copilot:1 Loading the font 'https://cdn.scite.ai/assets/fonts/scite-icons/scite-icons.woff2?v=5' violates the following Content Security Policy directive: "font-src github.githubassets.com". The action has been blocked.
chunk-EPOLDU6W.mjs:193 Matched leaf route at location "/copilot/c/67dc1bf6-c5f5-4caf-b365-**********" does not have an element or Component. This means it will render an <Outlet /> with a null value by default resulting in an "empty" page.
ex @ chunk-EPOLDU6W.mjs:193

api.individual.githubcopilot.com/github/chat/threads/67dc1bf6-c5f5-4caf-b365-********/messages:1  Failed to load resource: the server responded with a status of 403 ()

[Aimran42]

Ok That's a serious problem right there 😭

[JMTDI]

Same issue here. Two specific chats show "Access denied — Single sign-on to view this chat" but all other chats work fine. Copilot Pro+ on a personal account. Has anyone found a fix?

[Zilleabbas10]

Same here.. It was working fine few minutes ago and now it is not working

[d1msk1y]

I'm having the same issue, hope it will be resolved soon. I had a massive prompt in that chat, which took me a lot of time to perfect

It's also sending 403 on that request as well as error: thread not authorized in response

[Arisetial-h]

Refreshed it, sign out and sign in again, still on the same issue

[joakee]

Having the same issue. Tried all troubleshooting techniques discussed and have also had no suvccess.

[Aimran42]

Hey Bud, this actually happens often
Quick fixes (try in order):

Hard refresh — Ctrl + F5
Log out and log back into GitHub
Try a different browser or incognito mode
Disable all browser extensions

If none of those work:
The 403 error is a server-side issue meaning GitHub's backend has lost authorization for that specific chat thread. At this point the only real solution is to contact GitHub Support directly at support.github.com and include the chat thread ID from your URL (the long string like 67dc1bf6-c5f5-4caf-b365-...). Mention that you're getting a 403 on the messages endpoint and "thread not authorized" in the response — that specific detail helps them locate the issue faster.

[aarsht7]

Hey bud to you too!

Here is the respond to your comment

#196191 (reply in thread)

[MooGoose449]

Same issue.

[Tfly6]

Same issue. This problem only occurred in one of my chat sessions. The other chat conversations are normal.

[Go2Engle]

having the same issue as well!

[despinozap-afex]

Same issue over here. I lost all the analysis gotten yesterday across my repos 😢