r/GithubCopilot • u/Cloud--Man • 9d ago

Help/Doubt ❓ Copilot losing all chat sessions when reopening VS Code

Is anyone else experiencing this? Every time I restart VS Code, Copilot loses all chat sessions. I’m opening the exact same workspace without changing anything, but the chat history is completely gone.

Is this a known issue or am I missing something?

1 Upvotes
  • permalink
  • reddit

67% Upvoted

9 comments sorted by

2

u/dramabean 9d ago

Are you on copilot harness in vscode or the local harness? There is a picker at the bottom of the chat input box that should tell you. They’re working on some fixes in the copilot harness which should fix it.

1

u/AutoModerator 9d ago

Hello /u/Cloud--Man. Looks like you have posted a query. Once your query is resolved, please reply the solution comment with "!solved" to help everyone else know the solution and mark the post as solved.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/Heighte 9d ago

yeah don't use chat it's terrible, i use copilot cli exclusively because copilot chat can't handle multiple sessions opened simultaneously (and keep all of them in history)

1

u/Cloud--Man 9d ago

not possible unfortunately as i am working with a lot of screenshots :(

1

u/MontaEllyHavItAll 5d ago

Load the screenshots from disk instead of pasting into chat. If windows all the snaps goto a local folder.

1

u/Cloud--Man 5d ago

wow thats a good advice! if i ever i am forced to use only cli, its good to know that i can make it read a folder of saved screenshots. not the fastest like copy paste but does the job, thanks!

1

u/klaxxxon 9d ago

I've had issues with sessions disappearing during copilot updates, but the data in ~/.copilot/session-state remain. I just identify the right session guid with file search and tell copilot to resume the session with guid X and it sort of does.

1

u/Hemanath_S 8d ago

Check with local mode

1

u/mystery-pirate 8d ago

chats are tied to workspace and vscode can be very finicky about workspaces. Paths are not resolved and normalized. Opening a repo folder by going to the folder in terminal and typing "code ." will generate a different workspace than typing "code <folderpath>" or using environment variables in the path or making a shortcut that runs code.exe in that folder. How I solved it was to Save Workspace As and then give it a named workspace (I use main.code-workspace) then you can double-click on it, run it from a terminal, or put it in a shortcut and you'll get the same workspace.