run_terminal_command fails with "spawn UNKNOWN" on Windows CMD environment

[stockautotrader]

Before submitting your bug report

• I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
• I'm not able to find a related conversation on GitHub discussions that reports the same bug
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: Windows 10
- Continue version: 1.2.22
- IDE version: VSCode 1.99
- Model: Claude Sonnet 3.6 (Anthropic provider via internal API gateway)
- config:

name: Local Config
version: 1.0.0
schema: v1
models:
  - name: Claude sonnet-4-6
    provider: anthropic
    model: claude-sonnet-4-6
    apiBase: https://internal-apigw-kr.hmg-corp.io/hchat-in/api/v3/claude


---

4. Description

Description

run_terminal_command tool fails in Agent mode with the following error:

run_terminal_command failed with the message: spawn UNKNOWN

All other tools (file edit, search, etc.) work correctly in Agent mode.
Only run_terminal_command is affected.

PowerShell is unavailable due to corporate security policy.
Command Prompt (cmd.exe) is the only available terminal profile.

Suspected cause: Continue may be attempting to spawn a child process via
Node.js child_process.spawn directly instead of using the VS Code Terminal API,
which appears to be incompatible with CMD-only environments.

To reproduce

1. Set VS Code default terminal profile to Command Prompt (cmd.exe)
2. Add the following to settings.json:
   "continue.terminalProfile": "Command Prompt"
3. Open Continue in VS Code and switch to Agent mode
4. Open a terminal session in VS Code (cmd.exe)
5. Ask the agent to run any terminal command
   (e.g. "Run echo %USERNAME% in the terminal")
6. Observe the error:
   "run_terminal_command failed with the message: spawn UNKNOWN"

Log output

No log files found.
The logs directory does not exist under %USERPROFILE%\.continue\