Cursor cannot read powershell's output

[dawidgrey]

[Luma]

One million percent this. Using Powershell + cursor is a nightmare. Tons of wrong tool calls and unread outputs

[soorfett]

I haven’t had that issue, but I wonder if the cursor devs develop on linux and hence aren’t so focused on powershell.

It does cause lots of issues. I suspect some can be fixed with better models/prompting (like getting confused about what shell is being used).

[secprobe]

The wording sounds strange!

I can’t see the console output in [your terminal].
that you see in [your console]?

Well, it’s not Powershell’s fault.
Try my workaround.

How Powershell becomes more pleasant for the agent

The entire terminal intigration is dirty and should be cleaned. This was probably taken 1:1 from VScode, but that does not work for the IDE for cursor, makes the agent partially blind and causes race conditions. Powershell without customization is an imposition. Use Powershell 7.5 and remove the content from shellIntegration.ps1 and replace it with # --------------------------------------------------------------------------------------------- # Copyright (c) Microsoft Corporation. All rights …