[FEATURE] VS Code Extension (Beta) regression: Configure "current working directory" (CWD)

[jconley88]

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

This issue refers to the 2.0.5 beta version of the Claude VSCode extension.

Previously it was possible to change the cwd of a claude session by /quit -> cd [...] -> claude
Alternatively /add-dir could be used to add necessary directories.

The lack of either of these features reduces capabilities in a multiroot/project workspace. All projects cannot be added to context.

Proposed Solution

I would like to be able to specify my project's parent directory (or any directory) as my claude cwd.

Alternative Solutions

Autodetecting the projects within a workspace may be a good solution if there is additional flexibility. I keep "system-level" context in the parent directory for claude that is not part of the workspace. I can place these anywhere as long as they can be added to context.

For the time being, I cannot use the beta version. As a workaround, I've configured the setting "claude-code.useTerminal": true to continue using the legacy version.

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

I have two (plus docs) projects nested in a parent directory that are developed in sync. Claude needs context on all in order to complete features. From the terminal, I open VSCode with > code my-project.code-workspace. When I open a claude panel, I'd like for it to

1. detect my root directory (where I ran the code command)
2. detect the three projects listed in the .code-workspace file
3. Add them all as directories
4. make it clear which directory of those is the current one when running bash commands

Additional Context

No response

[github-actions]

Found 3 possible duplicate issues:

1. VSCode Extension Regression: Multi-Root Workspace Context Not Switching Based on Active File Body: Environment #8559
2. [BUG] VS Code extension starts in an arbitrary workspace #8489
3. [BUG] Change folder is not "visible" to claude code in session #2001

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[github-actions]

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

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