Agents terminals are read only

[Artemonim]

@cdp @chand_priyankara @Aaa_Mmm

The Legacy Terminal option doesn't work anymore

Describe the Bug Legacy Terminal mode won’t activate in Cursor 2.2, nor after rolling back to Cursor 2.0. Now it always opens that ■■■■■■ terminal in read-only mode and without any text formatting. Steps to Reproduce I don’t know Screenshots / Screen Recordings [2025-12-11_14-36-32.png] Operating System Windows 10/11 Current Cursor Version (Menu → About Cursor → Copy) Version: 2.0.77 (system setup) VSCode Version: 1.99.3 Commit: ba90f2f88e4911312761abab9492c42442117cf0 Date: 2025-11-13T2…

The Legacy Terminal option doesn't work anymore

Cursor IDE: Legacy Terminal Tool is ignored / “randomly” works — Investigation Dossier Scope This dossier documents an investigation of Cursor IDE terminal behavior on Windows (Cursor 2.3.34, OS 10.0.22631). The user-facing issue: enabling “Legacy Terminal Tool” does not consistently give an interactive agent terminal; instead Cursor often uses a read-only / review-mode terminal. Occasionally, Legacy Terminal appears “randomly” in some chats. As requested, this file is laconic: evidence + what …

Priority support

Thank you for the details. I checked, your other post and the internal ticket we made from it are still pending for our engineers.

[deltaforce9 (Rick)]

This is absurd, I have been going through this for about a year, they finally fixed it last year with having legacy terminal in settings enable and now once updated to 2.3.x its doing the same old crap again. I have tried every possible thing and no matter what I do, cursor agent terminal is ALWAYS read only. That might be fine for most people but for me I NEED interactive terminal for most of my tasks. Now I am held hostage to stay locked at 2.2.x — this is getting really old. Why even have the use legacy terminal option if it does not work? @

Cursor, explain why this behavior has been regressed with latest updated versions PLEASE

[3apa3a (Djdolbit448)]

That helped me. “cursor.terminal.useLegacyTerminal”: true Add to settings.json, restart cursor

[Alex_Hope_O_Connor]

Setting the Legacy Terminal Tool no longer fixes this issue for me either.

[Ariyan (Ariyan Khan)]

not again! this same problem every time.

[Artemonim]

I even generated instructions on how to try to fix it, but they ignored me.

The Legacy Terminal option doesn't work anymore

@andrewh could you just run it using the Agent in the Cursor repo, with either GPT-5.2 XHigh or Opus 4.5 Thinking?

[Ariyan (Ariyan Khan)]

@Ariyan

is there any roundabout way to fix it? or which old version you are using?

is there any roundabout way to fix it? or which old version you are using?

[Artemonim]

Downgrade to 1.7.x worked, but this version is now disabled. Cursor Team simply turned on a server flag that prevented the good terminal from being used.