Hey, Justin. This is a different case. It’s not the markdown lexer and not an overgrown DB. The toast No remote extension installed to resolve wsl means that when Cursor tries to open the file, it has no active resolver for the vscode-remote://wsl+... URI. The status bar Disconnected from WSL: Ubuntu confirms it. The WSL connection dropped, and the window is trying to restore an already-open radial-chart-animation-usage_1907604c.plan.md cold, before the remote host is back up.
Checklist when this happens:
- Check that
anysphere.remote-wslis installed and enabled:F1→Extensions: Show Installed Extensions, Local section. If it was disabled by accident, enable it. You should not havems-vscode-remote.remote-wslfrom Microsoft installed. - Start the distro manually: in PowerShell run
wsl -d Ubuntu, and keep that terminal open. In yourwsl -l -v, Ubuntu is oftenStopped, and Cursor tries to connect to a stopped distro. - In Cursor run
F1→Developer: Reload Window. After reload, the plan tab should reopen through a working remote. - If you still get
No remote extension..., close all WSL tabs usingFile→Close Folder, then runF1→WSL: Connect to WSLand open the project viaFile→Open Recent. This avoids auto-restoring the tab before the resolver is up.
If you can reproduce it, send:
F1→Output→ channelRemote - WSL, text or a screenshotwsl -l -vright after the error, so we can see Ubuntu’s state at the moment it fails
With that, I can tell if the extension is breaking or if the WSL distro itself is crashing, for example after sleep. Similar pattern for context: [WSL] Remote connection unstable – “Open Folder” infinite loading + extension host never starts (NoResolverFound / transport provider)