[FEATURE] VSCode extension: surface conversation history from sibling git worktrees
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
Problem statement
The Claude Code VSCode extension scopes its conversation history panel strictly to the current workspace folder. When I create a git worktree of a project I've been working in and open the worktree in a new VSCode window, the extension's history panel is empty — none of the prior conversations from the main repo are accessible from the extension UI.
This breaks a common workflow: spinning off a worktree to do parallel work on a feature branch while wanting to continue (or at least reference) the conversation that led up to the branch.
Current behavior
- Main repo opened in VSCode → extension shows full session history for that project.
- Sibling worktree of the same repo opened in a new VSCode window → extension shows zero history, because the worktree's filesystem path hashes to a different
~/.claude/projects/<hashed-cwd>/directory. - No command-palette entry, button, or
claudeCode.*setting exposes cross-project or cross-worktree sessions. - The only workaround is to drop into the integrated terminal and run
claude --resume <uuid>, which resumes the conversation in the terminal TUI — not inside the extension panel.
Why it matters
Worktrees are the standard git answer to "work on two branches at once without stashing." Without history portability, users either lose continuity or are forced out of the extension into the terminal TUI — which defeats the point of using the extension.
Environment
- OS: Windows 11
- Claude Code VSCode extension (native)
- Storage scheme confirmed shared with CLI at
~/.claude/projects/<hashed-cwd>/*.jsonl
Proposed Solution
Proposed solution
Parity with the CLI's resume picker, exposed in the extension UI:
- Widen to sibling worktrees (CLI equivalent:
Ctrl+W) — a toggle/button in the history panel that lists sessions from any worktree of the same repository, identified via git (e.g.git worktree listor shared.git/common dir). - Show all projects (CLI equivalent:
Ctrl+A) — an opt-in toggle to surface sessions across every project on the machine, for cases where the worktree isn't tagged as a sibling. - Resuming a cross-worktree session from the panel should open it in the extension's side panel (not the terminal), the same as resuming a local session.
Suggested UI surface
- A small dropdown or filter chip at the top of the Session history panel:
This workspace/This repo (all worktrees)/All projects. - Corresponding command-palette commands:
Claude Code: Show Sessions From All Worktrees,Claude Code: Show Sessions From All Projects.
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Other
Use Case Example
_No response_
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗