claude-code - 💡(How to fix) Fix [VS Code Extension] Preserve input text across session navigation + multi-agent management [1 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#49168Fetched 2026-04-17 08:48:57
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Bug: Input text lost when switching between sessions

Steps to reproduce:

  1. Open the Claude Code VS Code extension with multiple sessions running
  2. Start typing a message in the input box of Session A
  3. Switch to Session B to check its progress
  4. Switch back to Session A

Expected: Draft text is preserved in the input box Actual: The typed text is gone — the input box is empty


Feature Request: Better multi-agent session management

Managing multiple concurrent Claude Code agents in VS Code is awkward compared to how Copilot handles parallel agent tasks. Would love to see:

  • A session list/panel showing all running agents with their current status (running, waiting, done)
  • Ability to name/label sessions
  • Visual indicator of which sessions need attention (e.g. waiting for input)
  • Quick switching between sessions without losing input state

This would make it much easier to parallelize work across multiple agents the way power users tend to operate.

extent analysis

TL;DR

The issue of lost input text when switching between sessions in the Claude Code VS Code extension may be mitigated by preserving the input state across sessions.

Guidance

  • The problem seems to stem from the extension not storing or retrieving the draft text when switching between sessions, suggesting a need for session-specific input state management.
  • To verify the issue, follow the provided steps to reproduce and observe if the input text is indeed lost when switching sessions.
  • A potential workaround could involve manually storing the input text before switching sessions, though this is not a scalable solution.
  • The feature request for better multi-agent session management, including a session list/panel and the ability to name/label sessions, could address the underlying issue by providing a more robust session management system.

Example

No specific code snippet can be provided without more details on the extension's internal implementation. However, the solution might involve using VS Code's API to store and retrieve session-specific data.

Notes

The provided information does not specify how the extension currently handles session data or input state, making it difficult to provide a precise fix. The feature request suggests a broader overhaul of session management could resolve the issue.

Recommendation

Apply a workaround, such as manually storing input text or using an external note-taking tool to preserve draft text when switching sessions, until a more comprehensive session management feature is implemented.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING