Would
Do we have an official chance log yet?
Thatās kind of how beta goes, brother. If they had everything vetted and documented it would not be a prerelease right? Haha
Unfortunately on 1.5.4 the terminal still fails the vast majority of the time, with cursor never recognizing the terminal command has completed and waiting forever.
Windows cursor with a WSL terminal, or cursor running directly in WSL. Fresh ubuntu install, bash.
I have had the same problem with the terminal integration in Cursor on W11+WSL2/Ubuntu.
Iāve reported the issue in the Bug Reports area. It might help, if you could add your experiences to that bug report.
IMO, this is one of the most devastatingly severe bugs Cursor has, as it effectively renders Cursor utterly useless on Windows. I donāt know why it is not being addressed, but I have had this issue since spring. I did some fairly extensive research on it, and sent a bunch of emails to a Cursor rep a while back. I should probably bring those details into the Bug Report here.
I think ANYONE who is having this issue, needs to open up bug reports. I donāt think Cursorās dev team understands just how severe the issues with terminal integration on Windows with WSL2 are. It effectively renders Cursor unusable, and IMO everyone who has spent time trying to use Cursor on windows, is due a refund because of how utterly debilitating this issue is.
But, the squeaky wheel gets the oil, and people really need to REPORT, REPORT, REPORT this issue until it gets through the Cursor teamās blinders that this is a SEVERE level issue.
Thanks for this - fixed it and releasing fix tomorrow
We have not forgotten WSL terminal issues - we have a team member working on it full time right now.
Ok, glad to hear! First Iāve heard that, but glad to hear. I have another project I have that is currently dependent on windows, and its been shut down for a while now because of the terminal integration issues in Win+WSL2.
Please fix all the UI bugs, 1.4.6 is barely usable:
- Go back/restore button missing most of the time
- Random model switches on mode changes (If this is a feature with some logic, make it switchable)
- āFinishā ding totally random (most of the time not working)
- Edit āmodeā icon gone (still clickable area)
I have no idea, what āKeep changesā is actually doing, and makes any sense (the files are changed already). Annoys me to have to press it every time, itās an agent after all.
āKeepā means the changes will be kept, and āundoā means the changes will be reverted. You are right, the file is already saved with the changes. That is why it says ākeepā because you already have the changes. If it was āacceptā youād think by clicking, the changes were getting added then.
You can also just press āKeep Allā if you donāt care about reviewing the code.
the multiline issue is resolved in 1.5.4 but it is still not possible to edit, after each letter it looses focus and I have to copy paste from somewhere else
I simply click in the terminal box to focus it and press enter, then the agent continues. Every now and then i have to do it twice, likely nested.
The app does a poor job either closing or reusing terminals too. After a couple hours of work I often have 20 or so bash.exe instances running. Not sure if related.
oh ya that would be a big loss if thatās removedā¦i use it all the timeā¦i wonder if there is something planned to replace it? I love being able to redirect instead of approve or skip
This is the update with the least functional changes, the most UI tweaks, and the highest number of bugs so far.
Could you share any more detail on the bugs?
Hey! We replaced this with āReject,ā but the behavior is the same if you provide an additional message in the prompt box
When I instruct the cursor to change the code, it endlessly repeats adding and deleting changes.
What is happening?
Version: 1.5.5 (user setup)
Commit: 1.99.3
Date: 823f58d4f60b795a6aefb9955933f3a2f0331d70
Electron: 2025-08-25T17:40:25.290Z
ElectronBuildId: 34.5.8
Chromium: undefined
Node.js: 132.0.6834.210
V8: 20.19.1
OS: 13.2.152.41-electron.0



