Downgrading works as a valid workaround. Thanks for sharing the link.
Some side-effects are inevitable in the process of continuous improvement, but I hope the dev team can address this issue soon.
2 Likes
Hope this can be fix soon. Downgrading is a temporary solution…
You can ask the cursor AI to kill the terminal process but then it uses a request plus it does a brute force kill which doesn’t necessarily give a clean termination.
I actually have a rule to always let me kill the terminal process and this used to work well. Please fix this…
What the hell guys… that’s crazy how no one in the Cursor dev team noticed this would be a terrible idea!
The agent terminals being read-only is breaking everyone’s workflow. We used to have full control over our terminals, and now we can’t even kill processes cleanly. The agent has to use brute force kills which don’t give clean termination.
This is a massive step backwards in usability. At minimum, give us a setting to make agent terminals editable again. We’re developers - we know what we’re doing and we need that control back.
This change is making Cursor less useful, not more useful. Please revert this or give us the option to disable it.
apart from that, I like it. good job haha
I would like to know the reasons for this change to the terminals. It’s cumbersome now.
A second problem is if you enter a terminal command and hit enter, it works. At this point if you hit enter again, nothing happens but if you start typing, text appears.
Describe the Bug
Cursor now runs terminals in non-interactive mode. No password prompts possible.
Before: Could enter sudo password when prompted
Now: “sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper”
Every sudo command fails. The AI just tells you to run it yourself in your actual terminal.
Can refactor entire codebases but can’t run sudo apt update.
Anyone else find this annoying?
Steps to Reproduce
Ask the ai to do any sudo related command on your host
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.6.23
VSCode Version: 1.99.3
Commit: 9b5f3f4f2368631e3455d37672ca61b6dce85430
Date: 2025-09-15T21:49:07.231Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Linux x64 6.8.0-79-generic
5 Likes
I really don’t like this change! I had come to rely on the ability to fix/tweak/cancel/rerun commands in the agent’s terminal. This is a major hindrance.
1 Like
Any updates on this?
Piling on here - 1.6 is unusable for me because of this change. Reverting to 1.5. This is the not the first time I have had to revert to an earlier version of Cursor in over a year of steady use, but it is the first time since 1.3.x I believe. It’s sad that this can still happen after all the improvements to the release process.
Adding my name to the mix. The read-only terminal has created major problems with our workflow. Why not let the developer choose to interact or not, rather than forcing read-only? I’m sure there were some reasons, but perhaps there’s a way to achieve them without read-only terminals. Hoping… 
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
The “read-only” terminals in 1.6 are unusable for me, and I have been forced to revert to 1.5. I must not be the only one with this problem. Dev server management has been a problem for me since I started using Cursor over a year ago. My platform is Node / React based. The agent constantly wants to restart the dev server to test changes, resulting in duplicate server processes running on the wrong port. I have tried many different rule schemes to manage this without success. At least I have had the option of terminating the server process manually so I can ensure there is a single dev server running on the correct port. Now for some reason in 1.6 the terminal has been made read-only and I cannot terminate the processes running there. The net result is a huge number of stray dev servers, due to multiple agent restarts, and I have to kill the processes manually outside the IDE.
Steps to Reproduce
Use Cursor on a Node-based project and wait until the Agent starts a dev server. Then use it some more until the agent starts another dev server. Massive pain-in-the-■■■ follows.
Expected Behavior
Make the ^%$$#@$ terminals not “Read Only” so developers have control over their development environment again.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.5.5
VSCode Version: 1.99.3
Commit: 823f58d4f60b795a6aefb9955933f3a2f0331d70
Date: 2025-08-25T17:40:25.290Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
Does this stop you from using Cursor
No - Cursor works, but with this issue
1 Like
Adding to the sentiment here - what’s the deal with this change? Would love to see it reverted, this screws up how I was using Cursor. For example, there is no quick way for me to refresh/restart my app that’s running in simulator
Yeah. same here. was working perfectly before now i cant use interactive terminal anymore…
I tried it, but this did not work. Only option was to run pkill.
Oh okay, I might be just lucky then because dotnet dies along the terminal. I suppose some other program would not.
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
The agent ran an npm run script to verify it’s changes, but did not kill it after. Moreover, the terminal is read-only so it’s dangling. Even after explicitly asking it to close the server, the agent tried pkill to kill it, which did not kill it.
Steps to Reproduce
Create a vite project. Ask the agent to do some changes to the project, and verify them.
Expected Behavior
Long-running processes should show an option to be killed in the tool call UI. Or, remove read-only terminals.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.6.35 (user setup)
VSCode Version: 1.99.3
Commit: b753cece5c67c47cb5637199a5a5de2b7100c180
Date: 2025-09-19T17:39:38.846Z
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
Does this stop you from using Cursor
No - Cursor works, but with this issue
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
With recent update, the agent terminals are now read only which causes a lot of issues and gives less control. I don’t understand the reasoning for this.
Steps to Reproduce
have agent run any type of terminal commands
Expected Behavior
ability to update terminal commands in agent terminal window
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.6.35 (Universal)
VSCode Version: 1.99.3
Commit: b753cece5c67c47cb5637199a5a5de2b7100c180
Date: 2025-09-19T17:39:38.846Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
For AI issues: which model did you use?
claude-4-sonnet
Does this stop you from using Cursor
No - Cursor works, but with this issue
IT’S A TERRIBLE BUG! Without this feature, it cannot debug automatically: Add log → Read log → Modify code → Add log….
2 Likes
This change also interrupts my workflow. I use the cursor alongside myself when interacting with the terminal.
For those who want to stay 1.5:
Add these lines to User Settings JSON (press Ctrl + P)
"update.enableWindowsBackgroundUpdates": false,
"update.mode": "none"