Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

fix: use VSCode default terminal to find Claude CLI on Windows#465

Merged
breaking-brake merged 1 commit intomainbreaking-brake/cc-wf-studio:mainfrom
fix/windows-claude-cli-path-463breaking-brake/cc-wf-studio:fix/windows-claude-cli-path-463Copy head branch name to clipboard
Jan 17, 2026
Merged

fix: use VSCode default terminal to find Claude CLI on Windows#465
breaking-brake merged 1 commit intomainbreaking-brake/cc-wf-studio:mainfrom
fix/windows-claude-cli-path-463breaking-brake/cc-wf-studio:fix/windows-claude-cli-path-463Copy head branch name to clipboard

Conversation

@breaking-brake
Copy link
Copy Markdown
Owner

Problem

When running Claude Code CLI in Windows environment, npx is not recognized.

Current Behavior

  1. Launch VSCode from GUI
  2. ❌ Extension Host doesn't inherit shell PATH environment variable
  3. claude command not found, falls back to npx claude
  4. npx is also not in PATH, execution fails
'npx' is not recognized as an internal or external command,
operable program or batch file.

Expected Behavior

  1. Launch VSCode from GUI
  2. ✅ Get shell from VSCode's default terminal setting
  3. ✅ Get PATH environment variable via login shell
  4. ✅ Correctly detect and execute claude or npx

Solution

Use VSCode's default terminal setting (terminal.integrated.defaultProfile) to respect user's shell configuration.

Changes

File: src/extension/services/claude-cli-path.ts

  • Read VSCode's terminal.integrated.defaultProfile.{platform} setting
  • Spawn login shell with configured shell to execute which (Unix) or Get-Command (Windows)
  • Fallback when VSCode setting is not configured:
    • Windows: pwsh → powershell
    • Unix: zsh → bash
  • Support version managers (mise, nvm, fnm, volta)

Impact

  • Works on Windows/macOS/Linux
  • Can detect CLI tools installed via version managers
  • Respects VSCode terminal settings (behaves as user expects)

Testing

  • Manual E2E testing on macOS completed
  • Manual E2E testing on Windows completed
  • AI workflow generation (Generate with AI)
  • AI workflow refinement (Refinement Chat Panel)
  • AI workflow name generation (Generate Name)
  • Code quality checks passed (npm run format && npm run lint && npm run check && npm run build)

Notes

🤖 Generated with Claude Code

- Use VSCode's terminal.integrated.defaultProfile setting
- Execute login shell to get user's full PATH environment
- Support version managers (mise, nvm, fnm, volta)
- Fallback to pwsh/powershell (Windows) or zsh/bash (Unix)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@breaking-brake breaking-brake merged commit dfa435b into main Jan 17, 2026
3 checks passed
@breaking-brake breaking-brake deleted the fix/windows-claude-cli-path-463 branch January 17, 2026 13:23
@breaking-brake breaking-brake mentioned this pull request Jan 17, 2026
braking-brake-semantic-release Bot pushed a commit that referenced this pull request Jan 17, 2026
## [3.15.3](v3.15.2...v3.15.3) (2026-01-17)

### Bug Fixes

* normalize CRLF line endings for Windows compatibility ([#464](#464)) ([d2e1c5f](d2e1c5f)), closes [#463](#463)
* use VSCode default terminal to find Claude CLI on Windows ([#465](#465)) ([dfa435b](dfa435b))
@braking-brake-semantic-release
Copy link
Copy Markdown

🎉 This PR is included in version 3.15.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Morty Proxy This is a proxified and sanitized view of the page, visit original site.