Skip to content

[Feature Request] Add workingDirectory setting to specify project root independently of VSCode workspace folder #14015

Description

@FantomaSkaRus1

Bug Description
Feature Request: workingDirectory setting for VSCode extension
Problem: When using Claude Code VSCode extension, it always starts in the currently opened folder. This is problematic for users with a monorepo-style structure:
D:\MegaCloud\ ← root with .claude/CLAUDE.md, Memory/, manifests
├── .claude/
│ ├── CLAUDE.md ← global rules & instructions
│ └── Memory/ ← persistent knowledge base
├── ProjectA/ ← individual project
├── ProjectB/ ← individual project
└── ProjectC/ ← individual project
When I open ProjectA in VSCode, Claude Code starts in D:\MegaCloud\ProjectA\ and cannot see the parent .claude/ directory with all my manifests, rules, and memory files. Current workarounds (all inconvenient):
Always open the root folder instead of specific projects — breaks project-focused workflow
Use multi-root workspace — extra complexity
Symlink .claude/ into every project — maintenance nightmare
Requested solution: Add workingDirectory (or projectRoot) option to settings.json:
{ "workingDirectory": "D:\MegaCloud" }
Or in VSCode settings:
{ "claude-code.workingDirectory": "D:\MegaCloud" }
This would allow Claude to always start from a specified root while still being invoked from any subfolder. Alternative: Allow CLAUDE.md inheritance — Claude looks for .claude/ not only in cwd but also in parent directories up to a configurable root.

Environment Info

  • Platform: win32
  • Terminal: null
  • Version: 2.0.69
  • Feedback ID: 9b3e9727-9c4e-4701-888a-a9f68cd9abd8

Metadata

Metadata

Assignees

No one assigned

    Labels

    duplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions