Tool Calls / Commands Hanging in Git Bash

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

My engineering team and I want to start using Cursor CLI in windows terminal with Git Bash as our preferred shell. But, any shell command like echo, date, pwd, all hang indefinitely and never execute rending the CLI tool completely unusable. In CMD or even Powershell, it all works fine, but Git Bash is absolutely the standard shell for our team and we would rather use a competitor’s CLI tool than switch our shell to a lesser option.

Happy to provide any more information as needed. Thank you!

Steps to Reproduce

In Windows Terminal, with Git Bash as default shell, tell the agent to try to run a shell command. lol

Expected Behavior

I expect the agent to run the shell command properly

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

braden.sanders@SAI0787 MINGW64 ~/dev
$ agent about
About Cursor CLI

CLI Version 2026.03.30-a5d3e17
Model Opus 4.6 1M Thinking
OS win32 (x64)
Terminal windows-terminal
Shell c:\program files\git\usr\bin\bash.exe
User Email [email protected]

braden.sanders@SAI0787 MINGW64 ~/dev
$

For AI issues: which model did you use?

Opus 4.6 1M Thinking

Does this stop you from using Cursor

Yes - Cursor is unusable

I’m having the same issue but on macOS. All terminal commands by the agent just hang forever.

Version: 2.6.22
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
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: Darwin arm64 24.6.0

Request ID: 00d9726b-a470-4b06-892e-dc9ede9013c5

UPDATE: enabling the legacy terminal in settings fixes the issue, so far very reliably. It 100% doesn’t work with legacy terminal disabled, and works fine with legacy terminal enabled (although not in current agent sessions, you have to start a new one!). Hopefully that’s helpful, because this is a huge usability issue.

FURTHER UPDATE: well, legacy terminal doesn’t load my PATH or other .zshrc env vars, so it’s pretty useless. However, I got it working with legacy terminal OFF by launching from my terminal using $ cursor from my repo directory, rather than launching via macOS. Terminal commands seem to be working normally now. So maybe the issue with the non-legacy terminal is related to the PATH variable being wrong, maybe it’s not even pointing to a valid shell?

I’m experiencing the same problem of the agent hanging indefinitely.

Version: 2.6.22 (system setup)
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
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

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

[Translated by GPT]
Whenever the read_lints tool is triggered within a bash terminal workflow, the process hangs indefinitely.
This occurs even if the command being executed originates from a bash session that invokes Python, which then calls cursor-agent.

Steps to Reproduce

Open a bash terminal.
Use bash to run a Python script.
Within the Python script, invoke a cursor-agent command that triggers the read_lints tool.
Observe that the process becomes stuck and does not return.

Operating System

Windows 10/11

Version Information

CLI Version 2026.03.30-a5d3e17 │
│ Model Composer 2 Fast │
│ OS win32 (x64) │
│ Terminal mintty │
│ Shell \git\usr\bin\bash.exe

Does this stop you from using Cursor

No - Cursor works, but with this issue