Major Regression in Agent Terminal Functionality

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In previous versions of Cursor the agents were able to write commands into the integrated persistent terminal at the bottom of the screen. It didn’t matter what terminal it was (I have the GIT BASH set up and previously it was working perfectly fine).

Now, after upgrading, the agents all timeout and fail to run the commands. Turning on ‘legacy terminal’ works as a workaround but you lose all of the functionality of having a persistent terminal that the agent can work in as well as everything the ‘profile’ gives you (alias’s/PATH variables/ect).

I am marking this as ‘sometimes stops me from using cursor’ however, with the functionality the way it is, I will not be using cursor at all. Having the Agent try and fail to run commands and force me to copy paste the commands, then copy paste the output is detrimental to a fast development workflow.

Steps to Reproduce

Launch Cursor
Make sure Cursor Settings → Agents → Legacy Terminal Tool is set to OFF
Make sure you have a terminal set up in the bottom terminal screen (Terminal-> New Terminal). For my usage I utilize Git Bash as my default.
Ask an agent to run the ls command
Agent sits and spins, then times out.

Expected Behavior

Agent should be able to type and interact with persistent integrated git bash terminal the same way it was in previous versions.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 2.4.22 (system setup)
VSCode Version: 1.105.1
Commit: 618c607a249dd7fd2ffc662c6531143833bebd40
Date: 2026-01-26T22:51:47.692Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.22631

For AI issues: which model did you use?

Auto, gpt 5.2 high

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. This is a known issue in version 2.4.22 (and 2.4.21). Agent terminal commands time out or don’t run at all.

Legacy Terminal won’t help here. Based on what you described, the issue is how the newer versions interact with persistent terminals. Other users confirmed that version 2.3.34 works reliably.

The most reliable option right now is to roll back to v2.3.34:

  • Download from Download · Cursor (pick version 2.3.34)
  • Fully close Cursor before installing
  • After installing, verify that agent commands work

Important: if you already used 2.4.x, your chats might break after downgrading. Other users reported incompatibility when rolling back.

If you can, please send logs from Developer Tools (Help > Toggle Developer Tools > Console) when the agent tries to run a command. The team knows about the issue, but extra details from your setup (Git Bash) could help.