Cursor AI Agent Shell Tool Hangs on All Commands (Windows)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor AI Agent Shell Tool Hangs on All Commands

Steps to Reproduce

Make a change, try to stage / commit. The command completes, but the agent hangs for ever

Expected Behavior

It should continue once the command is completed

Operating System

Windows 10/11

Version Information

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

Additional Information

UI is getting to the stage where simple fixes (see my previous reports) are never getting done, and are increasing product frustration - this is silly given these should be quick fixes, easy to implement with CursorAI.

Fixed by downgrading to (and turning off all upgrades):
Version: 3.5.38 (system setup)
VSCode Version: 1.105.1
Commit: 009bb5a3600dd98fe1c1f25798f767f686e14750
Date: 2026-05-26T21:32:06.537Z
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

Does this stop you from using Cursor

Yes - Cursor is unusable

8

This is a known bug affecting the agent’s shell tool on Windows. The agent uses a different terminal execution path than the integrated terminal, and on Windows it can fail to detect when commands have finished, producing the hang you’re seeing.

Our engineering team is actively investigating. No reliable workaround exists at this time, though one thing you could try as a long shot: switch the default terminal profile to Command Prompt (cmd.exe) instead of PowerShell, then retry the agent.

Your finding that 3.5.38 works while 3.6.31 doesn’t is helpful – we’ll use that to narrow down the regression. I’m merging this into an existing thread where we’re consolidating reports of this issue. Updates will be posted there once a fix ships.