c565bdc464
When the VS Code extension runs on Windows but connects to WSL, direct shell spawning fails because process.platform is "win32" but commands should execute in the Linux WSL environment. This caused: spawn powershell.exe ENOENT The fix detects this scenario and falls back to ide.runCommand(), letting VS Code handle the remote terminal execution properly. Fixes #9661 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Continue
Ship faster with Continuous AI
The future of coding isn't writing more code. It's delegating the boring parts, so you can build the interesting stuff
Get started in Mission Control, CLI (Headless Mode), or CLI (TUI mode)
Quick Install
npm i -g @continuedev/cli
cn
Cloud Agents
Set workflows to run automatically on PR opens, schedules, or any event trigger
CLI Agents
Watch workflows execute in real-time and approve decisions step-by-step from your terminal
IDE Agents
Trigger workflows from VS Code or JetBrains—let agents handle the refactoring while you keep coding
Contributing
Read the contributing guide, and join #contribute on Discord.