Agents terminals are read only

Discussions
81

yeah. I today wondered if cursor is made with cursor :wink: As bugs look familiar to what sometimes happen in the project, if not to control every step :wink:

So I finished with following algorithm:
When (not if, but when - as it definitely HAPPENS) terminal jump to read only mode. I close cursor, run 1.6.6. setup. After installation I run cursor and ask it to “run terminal command pwd” in new chat. it runs, I see that bash is working as expected (with input enabled).
Then I close cursor, run installation (now checked latest 1.7.33). And after installation - work in cursor with working terminal (bash) from the place it was before going “read only”. For some time (probably 1 hour, probably 1 day) I’m with normal cursor again… $))))

82

The User Experience we deserve :clap::clap::clap:

83

true. it’s the typical 2-3 monopolies type of problem.
The “what are you gonna do? leave?”
Because they still profit so much that they can afford becoming worse.

84

When I switch by Ctrl+E to agent window mode - terminals in this mode are read only. when I switch back to “old way” chats - terminal works.
Also it’s very funny to read introduction to agent window mode - “you may focus on chats, work in terminal and code editor if needed”. Hah.

85

Finally! Issue has been resolved in Version: 1.7.33 :rocket:

86

:eyes:

87

I work in 1.7.33
as I told - I had one time bug reappear, but since then it works. Though in agent window mode (ctrl+e switch to better view) - terminals are read only initially (and not bash)
So it’s “workarounded” - not fixed indeed unfortunately.

1 Like
88

come on Cursor team, just add an option to disable this s***

2 Likes
89

On 1.7.36 and opening agent chat in window mode does not fix this issue.

90

I downgraded to 1.5

1.5 works great, just downgrade version and keep working

1 Like
91

Thank you! I’ll look for this version now!

92

Same here. Cursor, at least for the ways I use it, is completely unusable now.
I guess back to 1.5… or time to give Windsurf another try…

93

Please fix this

94

Does web_search work in 1.5 or did they break it at the server level?

95

This needs to be fixed!

1 Like
96

Given this issue hasn’t been fixed for three weeks and the only recourse is to use 1.5, two versions behind the current version, I guess it’s time to get my team set up with Claude Code.

Versions 1.6 and 1.7 advertise some good new features, but as usual they don’t all work. I wasn’t able to get browser control working in 1.7. The terminal control issues have been plaguing Cursor for many months. There seems to be a deafness in the product team to user feedback, and a systematic inability on the part of the engineering team to fix critical user interface problems. This is a competitive space Cursor team!

1 Like
97

Disappointing. Is the only fix for this really to downgrade to 1.5?

98

has anyone found a hack to override this behaviour in new versions?

99

1.6 almost great

100

It was mentioned above, but it’s weird. It’s easier to downgrade.