Agents unable to read terminal commands output

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Agents get no output from terminal commands tool, including stdout, stderr and exit code.

Steps to Reproduce

Windows, project with a folder path with no special symbols except dots. Ask agent to test its command tool with a simple echo. It reports that no output is available except with required_permissions: ["all"] arg. Go to settings - inline editing - legacy terminal tool - switch on. Ask agent to test. Report is positive now.

Expected Behavior

Agents use terminal commands as usual.

Screenshots / Screen Recordings

Screenshot 2026-06-03 191020
Screenshot 2026-06-03 191020982Ă—952 52.6 KB

Screenshot 2026-06-03 191329
Screenshot 2026-06-03 191329947Ă—477 24.6 KB

Operating System

Windows 10/11

Version Information

Version: 3.6.31 (user setup)
VS Code Extension API: 1.105.1
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Date: 2026-05-31T17:46:29.630Z
Layout: glass
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
xterm.js: 6.1.0-beta.220
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Composer 2.5, GPT 5.5, GPT 5.4

For AI issues: add Request ID with privacy disabled

414c5731-a1d4-45b9-8155-10a1628ee75d

Additional Information

Steps were described for special repro case. For a common case, agents tend to silently ignore terminal tool errors or just add some remarks like “terminal is not working for some reason”. This form allows me to attach only single screenshot, although label says “screenshots”, which is annoying.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report with steps and the Request ID. This is a known bug on Windows. In the default sandbox, the agent terminal tool doesn’t return any output, no stdout, no stderr, and no exit code. We’re tracking the issue, but I can’t share a fix timeline yet.

Good news, the workaround you found does work. The legacy terminal tool Settings → inline editing → legacy terminal tool uses a different execution path and avoids the problematic sandbox, so you can keep it enabled until the bug is fixed.

I reported this to the team internally. Once there’s an update on the fix, I’ll reply in the thread.

Also thanks for the note about the form. It really only lets you attach one screenshot, I’ll pass that along.