[FEATURE] VSCode extension: no way to select active folder in multi-root workspace

[hichish]

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

In a multi-root VSCode workspace, Claude Code always uses the first folder as its working directory. There is no UI control, command palette command, or context menu option to switch which folder is active. The only workaround is to open a separate VSCode window per repo or use the CLI.

Proposed Solution

A way to select/switch the active working directory within a multi-root workspace session — e.g. a command palette option, a folder picker, or a right-click context menu entry in the Explorer.

Alternative Solutions

No response

Priority

Critical - Blocking my work

Feature Category

Developer tools/SDK

Use Case Example

No response

Additional Context

No response

[manjunath-satyamurthy]

Sharing a related pain point that stems from the same root cause:

Even if claude config living in a single working directory is acceptable, the problem is that a session has no concept of a VS Code workspace (.code-workspace file). VS Code workspaces let you group multiple unrelated repositories/folders into a named context — and that grouping is persistent across window reloads.

Since Claude Code sessions are tied to a directory rather than a workspace, any additional repos or folders that the agent needs to be aware of are lost when the session or VS Code window is reloaded. You have to manually re-add them every time.

Expected behavior: Starting a session from a VS Code workspace should restore the full set of workspace folders automatically, so the agent has the right context without manual re-configuration on every reload.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.