Agents terminals are read only

Discussions
101

oh i found the solution - enable legacy terminal in the new settings. the terminals will no longer be read-only. i hope they do not take this setting away.

5 Likes
102

Thanks for sharing - this fixed it for me.

For those looking, its under Cursor > Settings > Cursor Settings > Chat > Inline Editing & Terminal

1 Like
103

thanks cursor team, now we can finally fet back to work :smiley:

104
ChatGPT said:

But who thought it would be a good idea to make the terminal read-only?

105

O cursor é uma excelente solução, já ajudou bastante e eu vinha sempre esperando uma nova boa surpresa a cada atualização.

Mas essa de tornar o terminal não editável, impedindo até acessos remotos, que era uma das coisas que eu mais utilizava até pra resolver problemas em outros ambientes, foi de lascar totalmente

Praticamente virou o chatGPT Web…

Cara isso é péssimo e esse recurso precisa ser restaurado o quanto antes, dessa forma, a primeira solução que oferecer isso, sem dúvida, vai ser a mais utilizada no mundo..

E ta vindo aí uma chamada TRAE, ela já oferecia uns recursos interessantes, se ela permitir edições no terminal e acessos remotos a partir da IDE, eu e muito outros vamos acabar migrando, infelizmente.

Ah, e sem contar que é bem mais barata também…

Pessoal do CURSOR, nos ajudem a lhes ajudar…

106

For me on MacOS, Cursor > Settings > Cursor Settings > Chat > Inline Editing & Terminal > enable Legacy Terminal Tool

2 Likes
107

I can’t believe they actually did this. Seriously, thank you, I’ve been checking this thread every day.

But also, **** MacOS and the Apple cultists lol

The setting shows up fine for me on Linux, and as someone who doesn’t open random junk in Cursor or let it run commands unless they’re on an allow list, I really hope I’m never forced into that sandboxed version of the agent terminal again. The so-called ‘legacy’ one works perfectly a little risky, sure, but powerful as hell.

108

image
Perfect solution :heart: :heart: :heart:

3 Likes
109

The above solution for enabling Legacy Terminal Tool works for me :slight_smile: However, I want to reiterate this is a shocking change and goes against all the reasons why I’d use cursor over VSCode. AND this was done by default with an update. The agent can no longer do any actual agent work on terminals. Please revert this change as soon as possible and do not keep changing defaults without notifying users, you’ll lose customers real fast if you keep doing this…

1 Like