Hi, I’ve noticed that the agent terminal is now read-only, and this has become a problem. Many times, the agent successfully starts a server, but it doesn’t kill the process when needed. Since I can’t run commands directly in the agent’s terminal anymore, I have to manually find the process running…

Version: 1.6.27 (Universal) VSCode Version: 1.99.3 Commit: d750e54bba5cffada6d7b3d18e5688ba5e944ad0 Date: 2025-09-17T20:21:17.042Z (9 hrs ago) Electron: 34.5.8 Chromium: 132.0.6834.210 Node.js: 20.19.1 V8: 13.2.152.41-electron.0 OS: Darwin x64 24.0.0

I am not able to open expo as it requires typing a letter into the terminal to open the simulator..

Please bring back the edit capability in the agent terminals. We use it extensively to work with kubernetes clusters. We run few commands in the agent terminal to help the agent navigate the cluster, also provide temporary jwt authetication by running few commands manually in the terminal.

I’m not sure of macos, but can’t you just go to the Terminal tab at bottom and use trashbin to kill the terminal and process along it?

I’m on macOS 15.6.1 (Sequoia) and using zsh.

In case it helps convince the product team to undo this change – one of my use cases is to run pytests of temporal workflows. Sometimes these workflows hang and I need to interrupt. The agent is able to pick up the interrupt/errors and fix them. However, with this change, I can ctrl-c but that gi…

Version: 1.6.27 (user setup) VSCode Version: 1.99.3 Commit: d750e54bba5cffada6d7b3d18e5688ba5e944ad0 Date: 2025-09-17T20:21:17.042Z Electron: 34.5.8 Chromium: 132.0.6834.210 Node.js: 20.19.1 V8: 13.2.152.41-electron.0 OS: Windows_NT x64 10.0.26100 I can’t even copy from terminal window anym…

Same here, our entire R&D can’t work with cursor :frowning: Can you please provide an ETA for the rollback/fix? It’s really a deal breaker in our case

It has completely disrupted my workflow… Why are you trying to block interaction with a terminal? It makes no sense! I am a DevOps engineer and I need to interact with a terminal 80% of the time (killing processes, entering values, etc.). Please rollback this change.

Agents terminals are read only

Support Bug Reports

deanrie (Dean Rie) September 18, 2025, 2:45pm 12

Thanks everyone for the info. I’ve already notified the team about this issue, and I believe it’ll be fixed.

11 Likes

Topic		Replies	Views
Cursor v1.6 - Pre-release Discussion Discussions	177	8938	September 16, 2025
Cursor v1.5 - Release Discussions Release Discussions	263	13628	September 9, 2025
Terminal commands 100% broken Bug Reports	57	1952	October 31, 2025
Cursor agent mode - when running terminal commands often hangs up the terminal, requiring a click to pop it out in order to continue commands Bug Reports	115	31552	November 15, 2025
2.0 has lost a lot of functionality I can no longer use Cursor Feedback java	83	9420	February 9, 2026

Agents terminals are read only

Related topics