This is a known bug affecting the agent’s shell tool on Windows. The agent’s terminal execution path uses a different mechanism than the integrated terminal, and on Windows it can fail to capture command output - producing exactly the behavior you’re seeing (command starts but no stdout/stderr is returned).
Our engineering team is actively investigating this across several enterprise customers. No reliable workaround exists at this time unfortunately, though a few things you could try as a shot in the dark:
-
Switch the default terminal profile to Command Prompt (
cmd.exe) instead of PowerShell, then retry the agent -
Add this to your settings.json:
“terminal.integrated.shellIntegration.enabled”: false
Neither is guaranteed to help, but some users have had intermittent improvement with option 1.
You may also find this related thread useful — another Windows user reporting the same issue with active discussion.
I’m merging your thread into the existing one so all reports are consolidated. We’ll post an update there once a fix ships.