Long time VSCode on Windows user here. Obviously I use WSL2 as I would expect pretty much anyone doing development for non-MS technologies would. Cursor seems to be completely broken regarding WSL2 support. Some trawling around the forum brings up various threads from the past few months suggesting a) it’s been broken forever, b) cursor people aren’t interested in fixing it and c) there are some potential workarounds but vaguely specified and not documented properly. For clarity: the problem seems to have something to do with installing the WSL VSCode extension twice on the same machine. So if you never used VSCode on the machine it probably works, but that’s approximately nobody in the target audience.
So…does anyone have a canonical document describing the correct workaround?
If not I’d be happy to write that as I would really like to try cursor but can’t until it supports my (fairly common) environment. Any authoritative information on what worked would be helpful in that endeavor, thanks.