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

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-13T23:10:43.113Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.22631

Version: 2.2.14 (system setup)
VSCode Version: 1.105.1
Commit: 1685afce45886aa5579025ac7e077fc3d4369c50
Date: 2025-12-11T01:12:35.790Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.22631

For AI issues: add Request ID with privacy disabled

c6fefea0-7469-4f25-9301-e6cf2db308c3

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. I can’t repro this. Please try a quick reset:

  1. In Settings, turn off Legacy Terminal
  2. Fully close Cursor and make sure no Cursor processes are running in Task Manager
  3. Launch Cursor and turn Legacy Terminal back on

Let me know if this helped. If not, please send a fresh Request ID right after the attempt, plus logs from Help > Toggle Developer Tools > Console.

d327b0bb-c051-4e65-a051-020be1a1963e
vscode-app-1765497404811.zip (4.8 KB)


GPT-5.2 XHigh then performed a diagnostic of the problem. it was Interesting ~18/1.45 minutes/$ with ~80 tool calls.
RID: d3ccf4e0-84f4-4bba-bb1d-0447b1dc4b04

Translated answer:

I didn’t notice then how the current development was clogging up the system disk with garbage. There is free space on disk right now, but the situation is not changing.

Also suggest to remove/rename this and try again:

  • ...\AppData\Roaming\Cursor\User\globalStorage\state.vscdb
  • ...\AppData\Roaming\Cursor\User\globalStorage\state.vscdb.backup

I moved it away, open Cursor, switch to Legacy Terminal and terminal still in read-only.

I hope you will be able to offer me a solution to the problem before Monday, since my code launch and quality control system works through the terminal and it is extremely uncomfortable to work with the new terminal.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Normally, we could toggle on “Legacy Terminal Tool” and we type in the terminal that the agent uses, like the old and CORRECT functionality of agents using shell sessions.
I honestly at times feel like the developers of this IDE are treating us like children by making it read-only, making large functionality changes without giving us an option to opt out at first startup after upgrade. And now for some reason toggling that ON, doesn’t allow me to interact with the agent’s session when it has something wrong with it, making me waste a bunch of time and energy either finding another way to fix it, or having to play a guessing game of which version this IDE broke this legacy feature, and having to downgrade Cursor IDE over and over until I find one that actually works in the most functional of ways. I’m just trying to do work not fight with my IDE once every few weeks/months. Hope you understand my frustration. Just as an example, cursor was updated with a big UI change that I didn’t ask for, and honestly worse than the old one, and completely changed my layout without asking me first. How about a little tutorial of the new changes on first boot, and give a toggle to keep our old config how we had it, downgrade easily if we see a bug, to make the customer experience better? You all move way too fast I want to cry! :sob:

Steps to Reproduce

Toggle on, kill all existing terminals, restart Cursor IDE. Still an issue.

Expected Behavior

Read Only Agent Terminal

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.9
VSCode Version: 1.105.1
Commit: a86689c93e9fb11addfbefd29a6ec7c0a59175e0
Date: 2025-12-10T16:51:25.713Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

I remembered a couple more details: when my disk was clogged, I made updates directly on the clogged disk; Cursor Installer could neither install the update correctly nor roll back the update correctly; I downloaded a new version of the program from the website - it was (and still is) the system version, whereas before I had the user version.the installation version.

However, for my colleague in misfortune, Legacy Terminal simply stopped activating after the update, just like for me, so, probably, disk problems are unrelated.

I’ve been working with GPT-5.2 XHigh for over an hour, made a git commit and git push through the GUI, opened a new chat with Codex Max 5.1 XHigh and it suddenly launched Legacy Terminal…
2025-12-12_22-34-50

Now the read-only terminal opens again. I literally can’t work on my web project because Vite can only be closed via cancel and the agent thinks the console has executed with an error.

Same thing today morning here. Like last week, same problem. Deleting %appdata% cursor didn’t help anymore. Legace mode ON.

Working with the cursor is becoming annoying. I really like it, but I think it’s time to start looking for an alternative. Everything worked perfectly at first, but over time, problems have become more frequent.

1 Like

Tried:

  • launch with --disable-extensions
  • launch with --user-data-dir "T:\Temp\cursor-clean"
  • Launch the second terminal in another chat to try to repeat the bug within the bug - both terminals are running in read-only mode.
  • echo $env:ELECTRON_RUN_AS_NODE gives an empty answer in my terminal and agent terminal
  • remove only "…\AppData\Local\Programs\Cursor"
  • +remove "…\AppData\Roaming\Cursor"
  1. Completely uninstalled Cursor (System) using Revo Uninstaller — it cleans all associated files and registry keys in the system.
  2. Installed Cursor (User).
  3. Logged in and enabled Legacy Terminal.
  4. Without opening a project, the Agent launched a good terminal.
  5. After opening a project, the Agent also launched a good terminal.

@deanrie @Jordan_Trujillo @skrzypekPL

I opened another project and in it, your new ■■■■■■ terminal launched again, which leaves zombie processes when it runs that are unkillable when it closes and doesn’t let user interact with it :roll_eyes:

Do you even use Cursor IDE within your team, or do you only code through Claude Code and the Codex CLI? I filed a bug report about zombie processes two months ago — in my latest version this bug has happened again and Vite stayed running, even when I clicked “Kill” inside Cursor and closed Cursor — I can still connect to the host that was started by that process!
For some reason, the “bad” legacy terminal does not allow itself to do this, but your “good” terminal does.

Or do your Agent not use a terminal? How do you even work then? Do you manually check everything and run all scripts manually too?

Downgraded to 1.7.54

sience my last post where i cryed about cursor i did small shopping and started new session. since like 16:00 it works perfectly, not ever 1 chat or app restart!!!

I tried updating to 2.2.20, the legacy terminal started for a while, but now it starts read-only again. Downgraded again.

1 Like

@deanrie any news, any help?

@Colin I would be grateful if someone would try to help me :backhand_index_pointing_right::backhand_index_pointing_left::flushed_face:

The Legacy Terminal launches occasionally, while the new terminal launches frequently. I don’t change anything in the Cursor settings.

I’m attaching the RID, but it was generated in private mode: feffc09b-9b4a-4a1c-b074-f149a1485f14

It happened again :frowning:
RID: 9d626b46-d47b-4102-9fa3-6197ac73a0f1

Version: 2.3.14 (system setup)
VSCode Version: 1.105.1
Commit: b3e9fe6c37659159fc2dec9ae643d74c25e5d0d0
Date: 2025-12-29T23:26:25.365Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.22631