Well you guys had the terminal issues squared away but now it looks like Cursor is completely ignoring the Legacy Terminal tool setting. I am guessing this is the issue because when I instruct Cursor to use custom aliases I have in my bashrc file, it says those commands are not found. When it tried …

Alright, that makes more sense now. Cursor is switching into a WSL environment instead of your main Windows setup with Laravel Herd. Try this: Step 1: Start without extensions Fully close Cursor Open Command Prompt and run:cursor --disable-extensions Try starting Agent Terminal and check if it…

Hey, thanks for the report. This is a known issue with the new Agent Terminal implementation in Cursor 2.x. The sandbox environment doesn’t load the user shell profile (.bashrc) or PATH. Try this: Step 1: Enable the Legacy Terminal Tool Open Cursor Settings Cmd/Ctrl+Shift+J Go to Agents → Inlin…

I have been using Legacy mode for a few months now. It has the same problem, as far as I can tell…it does not seem to load any kind of shell resource file. I have actually tried to set up custom integrated profiles. As far as I have been able to tell, those ONLY affect the interactive terminals you …

[image] Wish Born: It also says “Agent Terminal” instead of Cursor like it did before. [image] The Legacy Terminal option doesn't work anymore Bug Reports Describe the Bug Legacy Terminal mode won’t activate in Cursor 2.2, nor after rolling back to Curso…

yes as stated, I do have the Legacy Terminal setting on but Cursor is ignoring that settings. This is what I have for terminal setting in my user json file. “terminal.integrated.defaultProfile.windows”: “Git Bash”, This issue is causing very strange behavior. The terminal the agent is trying to u…

ok what seems to be happening is that Cursor is trying to use WSL to execute terminal commands but it shouldn’t. I’m not sure how to verify this but that would explain why the terminal says I’m using a version of PHP that isn’t even installed on my machine (I use Laravel Herd for dev environments). …

disabling all WSL extensions seems to have worked.

The terminal keeps using agents terminals despite the option “Legacy terminals” enabled

Terminal issues...again

Support Help

Artemonim (Artemonim) January 9, 2026, 11:15pm 5

Try to reboot your PC. It may help for some time.

Topic		Replies	Views
Terminals hanging CONSTANTLY since latest Cursor updates! Bug Reports terminal , performance	12	428	January 29, 2026
Terminal is completely broken Bug Reports	2	216	October 20, 2025
Agent terminal - powershell - no longer cmd.exe? Bug Reports	6	785	October 9, 2025
Unbelievable shoddy pile of garbage terminal handling Bug Reports	8	272	December 9, 2025
Agents terminals are read only Bug Reports java	132	4644	March 9, 2026

Terminal issues...again

Related topics