This is frustrating. I have to keep rolling back to version 1.5.11 just to get rid of this.
would be good to hear if this is being taken care of by the cursor team or if this is here to stay? Bc it does not work for me
This needs to be reverted asap its a workflow killer
+1 this is awful, if you are going to do things like this, make it a preference, not mandatory.
Also, it is frustrating that it cannot use bash instead of zsh because zsh is not set up with the NVM and other tools because I do not use it because zsh has a horrible completions implementation. MacOS.
FIX IT CURSOR. This is ridiculous. Cannot ever enter passwords or move/enter terminal selector for options when it is started by the agent.
2 Likes
Any work around with this?
i think this is fixed in the most recent update. Maybe someone from cursor can confirm this?
Thanks god, I thought I am tripping on this. Its disgusting bug, and its unbelievable that the Cursor team thought this was a good idea.
Cursor agents cant login to my server anymore because I need to type password, no SUDO pass as well. Just fix it already!!!
Same problem..
This would be great to get fixed. I should be able to choose if i want this to be read-only or not.
I was shocked to see there’s no reply from Cursor team in here on this or did I miss it?
This is a huge issue for me as well as my projects frequently need a bit of intervention whether it be me entering my password for a sudo command or hitting enter to get past a hung net build command or something and now readonly prevents this. Did anyone find a workaround? It would be nice if they gave us the option to make it readonly or keep like it always has been!
1 Like
Lol, it’s been many days since I wrote here, and no one from the Cursor team is paying attention or responding to this thread…
1 Like
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
With the new update, the model’s terminal has become read-only, which causes frequent issues. I can no longer fix problems directly in that terminal, and I end up wasting requests just to tell the model that I can’t interact with it, so it uses echo commands as a workaround.
Additionally, the model doesn’t fully understand what I mean in such cases, which makes things even more frustrating.
It would be very helpful to have an option to enable write access in the terminal managed by Cursor, or alternatively, to revert the terminal back to its previous behavior.
Steps to Reproduce
It’s simple: just try setting up a Next.js project. The command npx create-next-app@latest asks you several questions during setup, but since the terminal is read-only, it gets stuck, and you can’t select any options.
Expected Behavior
Either the commands to run without needing my input or give the user write access to the cursor terminal, as it used to be
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.7.25 (user setup)
VSCode Version: 1.99.3
Commit: 429604585b94ab2b96a4dabff4660f41d5b7fb80
Date: 2025-09-30T15:26:29.622Z
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
For AI issues: which model did you use?
It doesn’t matter really, I got the same problem with all of them
Does this stop you from using Cursor
Yes - Cursor is unusable
Thanks to this so-called “feature improvement” (which feels more like a bug), I’ve been stuck on version 1.5.11 while two major updates have already rolled out. Sure, it’s a shame I can’t try the shiny new features in Cursor, but let’s not forget—it hasn’t even been a month since 1.5.11 came out. If a friend falls ill for a month and causes me a bit of inconvenience, I don’t immediately throw away the entire friendship—and I’m not planning to ditch Cursor just yet, either.
That said, I sincerely hope Cursor doesn’t turn into the software equivalent of a Japanese rice cooker: a department store of pointless features. (FYI: Japanese rice cookers have gone through a kind of dinosaur-style evolution. They don’t just cook rice anymore; they bake bread, grill meat, respond to voice commands with AI, let you schedule meals from your phone, and will even chat with you when you’re lonely. All very impressive. But at the end of the day, the only thing that really matters in a rice cooker is whether it makes good rice.)
1 Like
can you pls fix the read only terminal unable to pass the password to agent terminal
I was able to rollback to 1.6.6 (links are in the beginning of the thread) then upgrade to 1.7.11 (if to downgrade to 1.7.11 directly, then terminal is still read only, but if to upgrade from 1.6.6 then it works). Though I use bash terminal with Windows 10 as base system.
Also I added update disabling (thanx @y-rokutan Agents terminals are read only - #40 by y-rokutan )
In result my current build with working terminal:
Version: 1.7.11 (user setup)
VSCode Version: 1.99.3
Commit: 867f14c797c14c23a187097ea179bc97d215a7c0
Date: 2025-09-26T16:55:04.318Z
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.19045
But, of course, I look forward to new version with working terminal.
and after some time of working it just showed me “agent terminals are read only” and switched to some powershell functionality. even if I have “git bash” in settings. chat agent also indicates, that terminal is not bash anymore.
well, will reinstall 1.6.6. and 1.7.11 back…. And… Funny. It works again. … well. for 10 minutes. then falls to agent read only mode again.
I know this is kind of “crazy” to say but everyone has been very analytical and im here to just say…
uhm… why is this still an issue no one has fixed after so many updates?
Cursor has been trigger-happy with changes since the past month and it is absolutely annoying.
1st the pricing model fully changed, now agent only terminals.
What other amazing ideas, I wonder…
The “improvement” of the terminal is even worse than the price update in July. Then at least you could continue using the IDE, even if you overpaid more than you originally planned. Now, even throwing money at the screen won’t fix the problem.
I don’t understand at all how the Cursor team uses their IDE in their own projects if they allow so many bugs and harmful updates to be released in release and pre-release.
For example, 1.7.11: Canceling or killing the (Agent?) console leaves zombie processes can cause the Agent to start so many processes that it will cause the computer to freeze, and you will not be able to stop it without manually finding these processes in the task manager or restrart the computer, because even after closing the IDE, the processes do not close, since they are not even linked to the IDE (!) and are called separately.
The bug report is already a week old.