cursor got stuck in exactly the same way on exactly the same task. maybe the problem is my terminal config (something about PowerShell or about my terminal prompt that it doesn't like?) or the model?

read my PowerShell command history without even asking. I'm not a fan of that.

it's running each MCP server in its own separate windows terminal window. why?

here we go

how do I use the agent

i don't know where that error message went, but WSL in cursor seems to work just fine actually

they've improved the vscode UI in a couple of places, which is nice. when they imported my extensions it seems like they did not import information about which extensions are supposed to be disabled, which is not great

just installed cursor on windows and the first thing i see is a message telling me that i can't use WSL in cursor. not immediately encouraging...