When opening files with the cursor://vscode-remote/ssh-remote+myhost URI the first file should open in a new window, however, since the recent update every subsequent file, using the same URI should open in a new TAB, but it opens a new WINDOW.
All options (file and folder) to open in a new Windows are set to OFF, yet they still open in a new Window.
This worked fine in the previous version, and still works fine in VSCODE. It also works fine using the local URI’s
Please ask if any more information required.
Steps to Reproduce
Open two seperate cursor://vscode-remote/ssh-remote+myhost links from the same host. They should open in seperate tabs.
Expected Behavior
Any subsequent files opened with the cursor://vscode-remote/ssh-remote+myhost URI should open in a new TAB
Hey, thanks for the detailed report. This is a known regression. After the update, remote deeplinks like cursor://vscode-remote/ssh-remote+... stopped reusing the existing window and now open each file in a new window, even if open in new window is turned off. Local cursor://file/... links aren’t affected, which matches what you’re seeing. We’re already tracking the bug, but I can’t share an ETA for a fix yet.
You found the right workaround. On 3.0.16 the behavior is correct. As an alternative so you don’t have to stay on an older version, you can try opening files via the CLI:
cursor --remote ssh-remote+myhost /path/to/file
This usually reuses the already open remote window. See if it fits your workflow and let me know how it goes.
I can reproduce the same behavior on macOS. It used to reuse the existing remote window and open the file in a new tab, but after the latest update every SSH URI launches a new window instead. Hopefully this gets fixed in an upcoming release.
Hey @Jhon_Caleb, thanks for confirming. Yep, it’s the same known regression. After the remote-deeplinks update, remote deeplinks cursor://vscode-remote/ssh-remote+... stopped reusing the existing window and now open each file in a new window. Local cursor://file/... links aren’t affected.
We’re tracking the bug, but I can’t share an ETA for a fix yet. As a workaround, you can open files via the CLI, it usually reuses the already open remote window:
cursor --remote ssh-remote+myhost /path/to/file
If there’s an update on the fix, I’ll reply in the thread.
Hey, quick note: Update: Mode = none turns off automatic downloading and installing, but it doesn’t fully silence the Update recommended notification. On older versions, the server may show this nudge on every launch no matter what the setting is, and there isn’t a reliable way to remove it completely on an old version right now. This is a known noisy behavior, and I can’t share an ETA for a fix.
Basically, the best way to get rid of the notification is to move back to the latest version. Opening files will still work via the CLI method from the thread above. Let me know if that won’t work for you.