Feature request: share/attach conversation context across project folders (VS Code extension)

Summary

Claude Code (both CLI and VS Code extension) stores each session's history under ~/.claude/projects/<sanitized-absolute-path>/, scoped strictly to the literal working directory path. There's currently no supported way to:

1. View/include a project's history from a different folder while working in the current one.
2. Keep history attached to a project when the project folder is renamed or moved — the path-based key breaks silently and the session becomes orphaned in the old, now-nonexistent folder path, with no warning or migration.

Motivating scenario

• Working in a project folder in VS Code with the Claude Code extension (not the CLI).
• Renamed the folder (simple typo fix in the name).
• All prior conversation history for that project disappeared from the extension's Session History panel — it was still on disk under the old path, but there was no indication of that, and no built-in way to relink it to the renamed folder.
• The only way to recover it was manually locating the .jsonl transcript under ~/.claude/projects/<old-path>/ and copying it into ~/.claude/projects/<new-path>/ by hand.

More generally: users often want to bring context from one project into another related one (e.g., a shared client, a companion doc, a sibling repo) without leaving the VS Code panel or hand-editing files in ~/.claude/projects.

Request

For VS Code extension users specifically (where there's no terminal-based claude --resume --Ctrl+A workaround), it would help to have a simple, visual way to:

• Browse sessions from other project folders on the same machine, not just the current one (similar to what claude --resume + Ctrl+A already offers in the CLI, but inside the extension UI).
• "Attach" / include another folder's session context into the current chat, e.g. via a picker in the Session History panel.
• Detect (or let the user confirm) that a folder was renamed/moved, and re-associate its existing history instead of silently orphaning it.

Today this all requires manually finding and copying .jsonl files under ~/.claude/projects/, which is fragile, undiscoverable, and easy to get wrong.

Environment

• Claude Code VS Code extension, Windows 11