Sessions are not saved to chat history

[guipbrito]

When you close a session, it does not go to the chat history

[Vizards]

Thanks for the report. I need a bit more information to understand where this is happening, because chat history is mostly managed by VS Code / Copilot Chat rather than by this extension.

Could you please share:

1. VS Code version
2. Extension version
3. GitHub Copilot Chat version, if visible
4. Your environment: local VS Code, Remote-SSH, WSL, Codespaces, or another remote window
5. Which chat mode you used: Ask / Edit / Agent
6. The exact steps to reproduce the issue
7. Whether the same chat is saved when using a built-in Copilot model instead of DeepSeek
8. Any errors from Output -> DeepSeek or Developer: Toggle Developer Tools

Also, when you say “close a session”, do you mean closing the chat tab, reloading VS Code, closing the workspace, or starting a new chat?

Without those details I cannot tell whether this is a DeepSeek provider issue or a VS Code/Copilot Chat history issue.

[HuangHarrison]

我的在1.121版本之前就遇到这个问题了（当然1.121也存在），即使的很近的聊天记录也会丢失，目前我使用代理聊天模式会出现，其他模式还没试过。比如在某一会话中聊天，退出该会话后，会话栏就找不到该会话了，有时候又出现该会话。在Open in Agents模式下又还能看到会话历史记录。

[guipbrito]

@Vizards, here the info

VS Code version: 1.121
Extension version: 0.5.2
GitHub Copilot Chat version, if visible: 0.43.0
Your environment: local VS Code
It happens with all modes (edit, plan, agent)
The chats are saved normally for the built-in models

To reproduce, open a new chat session, then go back to the sessions history (ctrl + N, or clicking on the arrow)

Seems to be a random bug, I tested a few minutes ago and DeepSeek's chats are now appearing on the session history

[Vizards]

@guipbrito @HuangHarrison Could you please check whether you have either of these VS Code settings configured?

• chat.utilityModel
• chat.utilitySmallModel

If yes, are they set to a DeepSeek model, for example:

• deepseek/deepseek-v4-flash
• deepseek/deepseek-v4-pro

I found that in my local setup, Copilot Chat's background title-generation request was routed through DeepSeek via the utility model setting. With DeepSeek thinking enabled, that background title request can take longer than expected, which may delay the chat session title/history entry from appearing.

If you do not have these utility model settings configured, then your issue is likely a different path and I will keep investigating.

[vovler]

Had this issue a week or so ago.
Try this:

Make the llm run the reindex the session store

Then reset all filters

And then click on refresh agent sessions

[bjmc]

@vovler that worked for me. Is there any way to prevent them getting lost again?

[vovler]

@vovler that worked for me. Is there any way to prevent them getting lost again?

only happened to me once, so idk

[bjmc]

It's happened three times for me so far. I think it somehow has to do with not/being signed in to the Github account. I wonder if the plugin stores a cache of sessions online / looks there first before / instead of indexing local sessions.

[Vizards]

@bjmc This extension does not store, upload, index, or restore Copilot Chat sessions. It only registers DeepSeek as a VS Code language model provider and handles the model requests that VS Code sends to that provider.

So if sessions disappear from the chat history, or come back after reindexing / refreshing the session store, that is most likely happening in VS Code / GitHub Copilot Chat rather than in this extension.

Your guess about GitHub sign-in state may still be relevant, but it would also be on the VS Code / Copilot Chat side. If it happens again, the most useful comparison would be:

• whether it also happens with a built-in Copilot model
• whether signing out / signing back into GitHub changes the behavior
• whether the session returns after the reindex / refresh workaround above
• VS Code version and Copilot Chat version

If the same history issue happens with built-in Copilot models, it would be worth reporting upstream to VS Code / Copilot Chat.

[bjmc]

Hi @Vizards thank you for the response. I should have been clearer, when I said "the plugin" I meant the Github CoPilot plugin for VS Code, not your extension to the plugin. If the problem reoccurs for me, I'll try to reproduce it in vanilla CoPilot with one of the built-in models.

I fully agree with you that it's likely an upstream issue.

My operating theory (unconfirmed) is something like this:

• CoPilot plugin prefers to store sessions in the cloud.
• Their online storage doesn't always like/accept unfamiliar model strings.
• It then presents an "empty" cloud store, and you have to kick it and make it reindex local sessions as well.

Happy to close this as unverified until we have more concrete details.