Browser identity router

Link Helm

One link. The right browser profile.

Route external links by source application and domain, keeping work, personal, and client sessions in the browser identity where they belong.

Build from source
macOS 13+ / Windows 10/11 x64 / Linux XDG macOS, Windows, and Linux validated MIT licensed

Control without context switching

A quiet control surface for every incoming link

Set Link Helm as the default browser, define precise rules, preview routing decisions, and keep sensitive URL paths out of diagnostics.

Link Helm settings showing default browser, accessibility, routing controls, and browser profile testing
The current Link Helm settings interface on macOS.

Routing pipeline

Context in. Correct identity out.

Link Helm evaluates only the context needed to make a routing decision.

  1. 01

    Source application

    Mail, chat, calendar, or any app opening a web link.

  2. 02

    Link context

    Match by source application identifier and domain without retaining full URLs.

  3. 03

    Routing rule

    Choose a specified, active, global, or prompted destination.

  4. 04

    Browser profile

    Open the link in the browser-managed identity that fits the context.

Built for repeat use

Routing that stays explainable

Specific, ordered rules

Preview matches before relying on them, then reorder and export your configuration.

Bounded diagnostics

Diagnostics retain domains and stable identifiers, not paths, query values, or fragments.

Visible fallback behavior

Ask, reuse an active profile, open a target profile, or fail explicitly when a destination is unavailable.

Current support

Validated on macOS, Windows, and Linux

Chrome, Edge, Brave, and Firefox routing has been validated across all three desktop platforms.

PlatformBrowserStatus
macOS 13+Chrome, Edge, Brave, FirefoxValidated
Windows 10/11 x64Chrome, Edge, Brave, FirefoxValidated
Linux (X11/XDG)Chrome, Edge, Brave, FirefoxValidated

Source build

Package Link Helm for all three platforms

Install Rust stable, Tauri CLI 2, and each platform's native build prerequisites. Build on the target operating system; Linux packages require Linux system libraries.

Windows

Build the NSIS installer on Windows 10/11 x64 with Visual Studio Build Tools installed.

cd apps/desktop
cargo tauri build --bundles nsis

Output: target\release\bundle\nsis\

Windows x64
Full instructions

Linux

Build the Debian package and AppImage on Linux after installing WebKitGTK, AppIndicator, and XDG dependencies.

cd apps/desktop
cargo tauri build --bundles deb,appimage --no-sign

Output: target/release/bundle/{deb,appimage}/

Debian / Ubuntu AppImage
Full instructions