After Cursor has created a canvas - .tsx file if I try to open the canvas file Cursor state’s it’s unable to open the canvas:
“Unable to open … .tsx
Unable to resolve resource”
Hey, thanks for the report. This looks like a known issue with how Windows drive-letter paths like C:\... get parsed when you click a markdown link in chat. The URI scheme parser treats C: as the scheme, the path gets URL-encoded (like in your screenshot: C:%5CUsers%5CChris%5C...), and textModelResolverService can’t resolve it. This is a known bug, and there’s no ETA for a fix.
To confirm it’s the same issue, can you clarify a couple of things:
Does the error happen only when you click the canvas link in the agent output, or also when you open the file another way (double-click in Explorer, restored tab after restart)?
If you right-click the .canvas.tsx in the Explorer panel, choose Reveal in File Explorer, and open it from there (or from the Canvas tab if it was already open), does it open normally?
Workaround for now: open the canvas from the Canvas tab/view, not by clicking the path link in the agent message. If I get an update on the fix, I’ll post it here.
Hey, thanks for flagging this. Yep, this is a known issue with parsing Windows paths like C:\... when opening a canvas from a link in an agent message. It’s being tracked, but I can’t share an exact ETA for the fix yet.
For now, the workaround is the same: open the canvas from the Canvas tab/view, not by clicking the path in the agent’s reply.
If it helps us debug faster, can you share what Cursor version you’re on and which release track you’re using Stable or Early Access. As soon as there’s an update on the fix, I’ll post it in the thread.
