Skip to content

[Feature Request] VS Code Extension: Start session from specific folder via context menu or setting #19644

Description

@shwankim7

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

When using Claude Code VS Code extension in a monorepo, sessions always start from the workspace root. There's no way to start a session from a specific subdirectory (e.g., packages/backend/).

Current behavior:

  • VS Code extension always starts Claude session from workspace root
  • No option to specify a different starting directory
  • Must use terminal CLI as workaround: cd packages/backend && claude

Desired behavior:

  • Right-click on a folder in Explorer → "Start Claude Code Here"
  • Or: Command Palette option to select starting directory
  • Or: Setting like claude-code.workingDirectory per workspace folder

Proposed Solutions

Option A: Context menu

  • Right-click folder in Explorer → "Start Claude Code Session Here"

Option B: Command Palette

  • "Claude Code: Start Session in Folder..." → folder picker

Option C: Multi-root workspace awareness

  • In multi-root workspaces, start session based on active file's workspace folder

Workaround

Currently using terminal:

cd packages/backend
claude

But this loses VS Code extension benefits (inline diffs, plan review UI, etc.)

Alternative Solutions

No response

Priority

Medium - Would be very helpful

Feature Category

Developer tools/SDK

Use Case Example

In a monorepo structure:

monorepo/
├── CLAUDE.md              # Global rules
├── packages/
│   ├── backend/
│   │   └── CLAUDE.md      # Backend-specific rules (NestJS, GraphQL)
│   ├── frontend/
│   │   └── CLAUDE.md      # Frontend-specific rules (React)
│   └── mobile/
│       └── CLAUDE.md      # Mobile-specific rules (Flutter)

When working on backend only, I want Claude to:

  1. Start with packages/backend/ as working directory
  2. Focus context on that package
  3. Still inherit parent CLAUDE.md rules (which already works via upward traversal)

Currently, starting from root means:

  • Claude sees entire monorepo (unnecessary context)
  • More tokens consumed exploring irrelevant packages
  • Less focused responses

Additional Context

No response

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