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] Operatin…

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…

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 agen…

Completely uninstalled Cursor (System) using Revo Uninstaller — it cleans all associated files and registry keys in the system. Installed Cursor (User). Logged in and enabled Legacy Terminal. Without opening a project, the Agent launched a good terminal. After opening a project, the Agent also laun…

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:

[image] Artemonim: which leaves zombie processes when it runs that are unkillable when it closes 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 h…

[image] Artemonim: Legacy Terminal mode won’t activate in Cursor 2.2, nor after rolling back to Cursor 2.0. 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!!!

[image] Artemonim: Downgraded to 1.7.54 I tried updating to 2.2.20, the legacy terminal started for a while, but now it starts read-only again. Downgraded again.

[image] Artemonim: I tried updating to 2.2.20, the legacy terminal started for a while, but now it starts read-only again. Downgraded again. @deanrie any news, any help?

The Legacy Terminal option doesn't work anymore

Support Bug Reports

Artemonim (Artemonim) January 12, 2026, 2:09pm 27

Up!

Unable to restore chats when resetting settings due to Cursor crash

Topic		Replies	Views
Run terminal command hangs —interactive terminal works fine Bug Reports terminal , windows	7	141	June 22, 2026
[Windows] Agent terminal tool: no captured output (~0ms, exit 0) — integrated CMD works; Legacy Terminal enabled; PowerShell blocked by policy Bug Reports terminal , windows	7	170	April 14, 2026
Cursor can only access Terminal with legacy terminal tool on Bug Reports sandbox , terminal , windows	12	159	July 16, 2026
Agents no longer can access sql connections Bug Reports terminal , windows	9	177	April 7, 2026
Cursor version 2.1.39 has terminal bug Bug Reports	90	3504	December 17, 2025

The Legacy Terminal option doesn't work anymore

Related topics