Support claude config in all workspace folders and workspace file directory (multi-root workspaces)

[cveld]

Feature Request

In multi-root VS Code workspaces, Claude Code only scans the first/primary
workspace folder for claude config such as claude.md, .mcp.json, commands. This makes it unnecessarily hard to configure
Claude in multi-root setups.

Proposed behavior

Claude Code should scan for Claude config in:

1. All workspace folders listed in the .code-workspace file (not just the first)
2. The directory containing the .code-workspace file itself
3. User-level ~/.claude/.mcp.json (currently also not supported in the VS Code extension)

Current behavior

Only the first workspace folder root is scanned. This forces users to place Claude config
in a specific folder that may not be the most logical location
for their project structure.

Environment

• Claude Code VS Code extension
• Multi-root workspace

[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.