[FEATURE] [VSCODE] Add manual refresh (or automatic) for sessions when continue from other places
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Add a refresh button or automatic detection or something to force Claude Code to "reload" the current conversation. I use Claude Code in WSL2 typically from VS Code (via the extension), but sometimes the terminal. And I often transition back and forth between my desktop (running WSL) and my laptop (which I connect to my WSL machine via SSH & the VS Code SSH extensions).
And while I can reload vscode (or the extension host) to get Claude to re-read the session to continue with it in another location, it would be great to not have to.
This is also related to https://github.com/anthropics/claude-code/issues/33370, https://github.com/anthropics/claude-code/issues/33369
Proposed Solution
The BEST would be for Claude Code to be able to just instantly show the "live" conversation from where ever it was started/last interacted from. So I could have CC open in a terminal and in VS Code on either machine and they were just all "live"
Outside of that, having a periodic or even manual refresh would be much better than today.
Alternative Solutions
_No response_
Priority
High - Significant impact on productivity
Feature Category
Other
Use Case Example
I do all my work in WSL2 on a beefy desktop machine. During the day I work directly on that machine using VS Code + WSL and WSL terminals, while at night I often switch to my laptop and I connect to my WSL machine using VS Code + WSL and SSH terminals. So I would love a smoother transition from 1 place to another.
I also sometimes start a conversation in a terminal and "upgrade" to a vscode session, which is OK if vscode loads fresh, but if I already have the window open, then the transition doesn't load the up to date conversation
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗