Long-term Windows terminal issues

Describe the Bug

Cursor doesn’t seem to understand that a user is on Windows, and consistently makes mistakes with terminal commands, leading to hanging commands, incorrect commands, and repeated attempts to fix an issue.

It also consistently tries to quit terminals incorrectly.

The results often confuse the LLM, leading them to assume dirs/files don’t exist, or that there are issues where there are none.

Switching the default terminal to git bash seems to help in some areas, but doesn’t fix the issue.

Additionally, sometimes the LLM tries to access files in .cursorignore or .gitignore, and as it can’t, it assumes the files don’t exist. The LLM needs to know it can’t access these files and why.

Steps to Reproduce

Ask cursor to do various tasks where it might need to use the terminal on Windows 10.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.5 (user setup)
VSCode Version: 1.96.2
Commit: ef5eeb47a684b4c217dfaf0463aa7ea952f8ab90
Date: 2025-06-21T05:31:17.701Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2 Likes

Currently, only rules can be used to help LLM avoid making mistakes again. He also often executes “&&” in my PowerShell :upside_down_face:

Yeah and I also keep having issues when using themes like OhMyPosh, and PSReadLine some times bugs out but I fixed that with a rule “Before running the first command always run Set-PSReadLineOption -PredictionSource None -BellStyle None as we are seeing issues with PSReadLine”.

Seems Windows is a second class citizen :confused: