vscode links fail if active window/tab is an existing code or ssh session

[calebshay]

Checklist

• Using latest version on the App Store
• Read the docs
• Searched for existing GitHub issues

Configuration

Blink: v18.1.1.980 (App Store). Feb 24 2025
iPadOS: 18.3.1

Describe the bug

When opening a vscode link (from GitHub Codespaces), if I already have one running in Blink or my active blink tab is currently an active ssh connection, and I am not on a new empty Blink tab, Blink will either do nothing (in the case of the active tab being an existing code tab), or attempt to run code http://<my-new-codespace-url> inside of the running ssh session.

Blink should open a new tab first, before triggering a call to code in order to start a new codespace session in a new tab (or, alternatively, a new window). It might even make sense to have that be user configurable of whether handling vscode links should trigger a new window or a new tab.

[carloscabanero]

Putting this in the Icebox as the plan is to move Code to its own application.