I found that chat sessions from the past two days cannot be opened

[S-Sarayoot]

Select Topic Area

Product Feedback

GitHub Feature Area

Copilot

Body

I am using GitHub Copilot Chat with a paid subscription on VS Code.

Recently, I found that chat sessions from the past two days cannot be opened, and I encounter an error stating that the .json file cannot be read.
I did not delete any files or clear any cache, and I am still using the same device.

Honestly, this is extremely frustrating. I paid for this service, so why do I have to manually copy every single chat if I want to keep any records? If I have hundreds of messages, it makes absolutely no sense to expect users to do this by hand.

I expect you to provide a proper solution for restoring chat history or an official method to recover my chats.
Also, please add a reliable backup and cloud sync feature for chat history, especially for paid users.
This kind of basic functionality should be included for a paid product. Otherwise, it feels like you just don’t care about your customers.

[Raghu-2005]

GitHub Copilot Chat History Issue

It sounds like you’ve run into a GitHub Copilot Chat history issue where .json files for past sessions can’t be opened. Currently, Copilot Chat in VS Code stores conversation history locally on your device, and there isn’t yet an official cloud backup or sync feature. That means if those local files become corrupted or inaccessible, you may lose access to older chats.

What You Can Try Right Now

• Check if the chat history files are still present in your local VS Code storage folder (usually under your user profile directory in VS Code extensions).
• If the .json file is corrupted, you might still be able to open it manually with a text editor and salvage some content.
• Update to the latest version of VS Code and the Copilot extension to make sure it’s not a version-related bug.

Feedback

Your request for a proper backup, restore, and cloud sync feature is very valid — especially for paid users. Many others have also asked for this, and it would improve reliability and user trust. I recommend filing this under Product Feedback → Copilot (which you’ve already done) so GitHub can track it.

👉 Until GitHub implements sync, the safest workaround is to export/copy important chats manually or periodically back up your local VS Code storage folder.

[queenofcorgis]

Hey there! 👋

Thanks for posting in the GitHub Community, @S-Sarayoot ! We're happy you're here. You are more likely to get a useful response if you are posting in the applicable category. The Accessibility category is a place for our community to discuss and provide feedback on the digital accessibility of GitHub products. Digital accessibility means that GitHub tools, and technologies, are designed and developed so that people with disabilities can use them.

I've gone ahead and moved this to the correct category for you, Copilot Conversations. Good luck!

[IN-Neil]

Bumping this.

Recently wanted to try finding cursor alternatives, Have been trying out. GitHub co-pilot (pro) then came across as frustration. I had a very important chat history I wanted to continue from yesterday. I can see it in the history but it can't be opened. Only the ones from today. Only code editor where this has ever happened. considering moving to another one.