Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [FEATURE] [VSCODE] Add manual refresh (or automatic) for sessions when continue from other places [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46432•Fetched 2026-04-11 06:20:27
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
eamodioeamodio
Participants
eamodioeamodiogithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4commented ×1
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • 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

extent analysis

TL;DR

Implementing a refresh button or automatic detection mechanism in Claude Code could allow for seamless conversation transitions across different environments and devices.

Guidance

  • Investigate the feasibility of adding a refresh button to the Claude Code interface, allowing users to manually reload the current conversation.
  • Explore the possibility of implementing automatic detection, enabling Claude Code to instantly show the "live" conversation from wherever it was started or last interacted with.
  • Consider the related issues (https://github.com/anthropics/claude-code/issues/33370, https://github.com/anthropics/claude-code/issues/33369) and their potential impact on the proposed solution.
  • Evaluate the use of periodic refreshes as a potential workaround, if a more comprehensive solution is not immediately feasible.

Example

No specific code example is provided, as the issue focuses on feature requests and high-level solutions rather than specific implementation details.

Notes

The proposed solution aims to improve the user experience by enabling seamless transitions between different environments and devices. However, the implementation details and technical feasibility of such a feature are not explicitly discussed in the issue.

Recommendation

Apply a workaround, such as periodically reloading the VS Code extension or using a manual refresh mechanism, until a more comprehensive solution can be implemented. This approach can help mitigate the current productivity impact while a more permanent fix is developed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#API routing#API middleware#SSR setup#ISR setup#authentication setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING