When the agent runs commands in the project workspace (including trivial ones such as echo hello), the tool returns empty stdout/stderr, often with exit code 0 and ~0 ms elapsed time. That makes it impossible for the agent to show “complete terminal output” or to reliably infer success/failure from real command results.
Important observation: In the same scenario, Codex does not exhibit this problem—output and behavior look normal there. That suggests the root cause may not be “PowerShell vs cmd” alone, and is worth treating as a high-signal bug in Cursor’s command execution or output capture layer rather than dismissing it as shell configuration.
Questions:
Are there workarounds or alternative execution paths you recommend (e.g. different shell integration, settings, or diagnostics) while this is investigated?
Is there a plan to raise priority for this class of bugs, given it breaks a core agent workflow (run command → read output → iterate)?
Is there a target fix version or rough timeline you can share?
Environment (issue still reproduces on this build):
Cursor: 3.0.16 (system setup)
VS Code base: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z
Layout: editor
Build type: Stable
Release track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200