[Feature]: Allow choosing a specific external browser for links (desktop)

[szafranski]

Before submitting

• I searched existing issues, pull requests, and discussions and did not find a duplicate.
• I am describing a concrete use case, not just a general browser preference.

Area

apps/desktop and the existing browser link target setting in apps/web

Problem or use case

T3 Code currently lets desktop users open links in either T3 Code or Your default browser.

I use one browser as the OS default and a different browser application for development work. Links opened from T3 Code, such as local development servers, pull requests, CI results, and documentation, should consistently open in the development browser without changing the OS-wide default.

OS-level browser routers can handle this, but they require installing and configuring another application for a preference that only needs to apply to T3 Code.

Proposed solution

Add a third desktop-only value to Settings -> Integrations -> Browser -> Open links in:

• Your default browser
• T3 Code
• Other browser...

When Other browser... is selected, let the user choose a browser application. Store that choice locally on the desktop client. Apply it everywhere the existing setting currently routes a link to the system browser.

If the selected application is no longer available, fall back to the OS default browser.

Smallest useful scope

• Desktop only
• One selected browser application
• One setting for all supported links
• Local setting with no cross-device synchronization
• No browser profiles or command-line arguments
• No per-domain rules
• No separate choices for pull requests, terminal links, or other link types

Alternatives considered

• Keep using Your default browser.
• Use T3 Code's built-in browser.
• Use an OS-level browser router such as Velja, Finicky, Choosy, or BrowserTamer.

Related work

• #9339 added the existing choice between the OS default browser and T3 Code.
• #11403 discusses the primary action for file and pull request links, but still targets the default browser.
• #8335 proposed a separate preference for pull request links. This proposal does not add settings per link type. It adds one destination to the existing global link target setting.

Open question

Would maintainers consider this within scope for the desktop app, or should users rely on OS-level browser routing tools?