It’s a path resolving issue between window host and linux remote machine, not the network.
Yes. I use Remote Tunnel to connect Windows with Linux machine. The issue didn’t exist in v1.3. I am sure that a regression was introduced in Cursor v1.4. @condor
Concur this is still occuring - as @Erik_Z noted above - I can reliably do this by forcing the app to do work on code that is outside of the current project’s folder path - i.e. elsewhere on the system. That will cause it to submit the same console errors as @1821746019 noted:
If I return to the prior chat comment I made, and direct the app to NOT address code outside of the current project path, IO can remedy the situation, tho of course then the model loses the context of what it just wrote (whether I revert code or not, it will resolve the issue and allow me to continue the conversation).
– to confirm, this is when cursor on windows, and code/server is connected to remote linux via ssh.
– to double check - if I remove the errant context bubbles for the files that show that they are using the “fakey backslash filepaths” (i.e. like \home\user\coding\example.py - that is outside the current project path) - if I remove those from the @context reference - then I can sometimes submit the next inquiry