How to Route Links to Different Browsers and Profiles on Windows 11 with Browser Tamer

Browser Tamer tackles that problem by occupying Windows’ default-browser slot, then handing links to the browser or profile selected by its rules. Its open-source repository describes support for Windows and Linux, browser autodetection, rules, and scripting. The attraction is straightforward: keep several browsers without manually directing every external link.

MakeUseOf writer Oluwademilade Afolabi describes using it to separate work browsing from other tasks. The useful idea is not replacing one browser with another. It is replacing a single default destination with a small routing system.

What Browser Tamer controls—and what it does not​

Browser Tamer’s documentation describes a pipeline: receive a link, apply optional URL processing, evaluate rules, then launch the selected browser or profile. Rules can examine the URL or the application that opened it.

That makes the utility particularly relevant to links launched from email, chat applications, and documents. It is not a tab organizer, and installing it does not automatically redirect ordinary navigation inside an already-open browser.

The distinction matters when testing. Clicking a link on a webpage may never involve Windows’ default-browser handler. Clicking a web link in another application is the intended starting point.

Windows itself supports default associations by application and protocol, rather than offering a built-in per-website routing system in its Default apps interface. Browser Tamer adds its decision-making after Windows hands it a supported link.

The takeaway: think of it as a dispatcher for incoming links, not a remote control for every browser tab.

Set it up on Windows 11​

Have the browsers and profiles you intend to use configured before creating routing rules. Browser Tamer can discover existing installations; it cannot supply an account session you have never established.

The project documents this Windows installation command:

winget install aloneguid.bt

Alternatively, the developer distributes installers through the project’s GitHub releases.

Then configure the handoff:

1. Open Browser Tamer’s configuration window.
2. If the browser list is empty, select Discover system browsers.
3. In Windows 11, open Settings > Apps > Default apps.
4. Find and select Browser Tamer, then choose Set default.
5. Return to Browser Tamer, select your preferred fallback browser/profile, and use the heart control to make it the default destination.

Microsoft confirms that application defaults are configured through Settings > Apps > Default apps. Its documentation also explains that an application’s page exposes the file and link types it can handle. If routing does not begin, checking those associations is more useful than repeatedly editing browser rules.

There are two defaults here, serving different jobs:

• Windows’ default handler: Browser Tamer receives the link.
• Browser Tamer’s fallback: Your chosen browser/profile receives links without a matching rule, unless you enable the picker for unmatched links.

In Afolabi’s reported setup, Brave’s Personal profile served as the fallback. That is an example, not a requirement.

Route websites without creating overly broad rules​

To send a website to a particular browser or profile:

1. Select the destination profile in Browser Tamer.
2. Under Rules, choose + add.
3. Keep the rule type set to URL.
4. Enter the website’s domain.
5. Select Domain scope when the intention is website-based matching.

The project documentation says ordinary text rules are case-insensitive and use substring matching. Its scopes restrict where that matching occurs:

Domain scope avoids a common mistake: triggering a rule because a website’s name appears in another site’s path or query string.

However, Domain scope is not automatically an exact-hostname check. The documented operation remains substring matching within the domain portion. That is a reason to test rules carefully—and not treat routing to a familiar browser as proof that a destination is trustworthy.

Afolabi used a rule for MakeUseOf links to open them in Chrome while leaving other links to Brave. The same arrangement can separate a regularly used work service from general browsing without changing Windows defaults throughout the day.

Route by application—and test conflicts​

Browser Tamer also supports Process rules. In the MakeUseOf walkthrough, Afolabi selected an Edge profile, added a Process rule, and entered:

slack.exe

The intention was to send links launched by Slack to that Edge profile.

For another application, the project recommends using Task Manager to identify its executable name. Open Task Manager, locate the application, and use Go to details where available.

The important boundary is provenance. Copying a URL from Slack and opening it elsewhere does not preserve Slack as the launching application.

What happens when a Slack link also matches a website rule? Browser Tamer’s documentation says conflicting matches invoke its picker. Rather than assuming a rule wins, test the overlap.

Open Tools > Pipeline debugger, then:

1. Enter a representative URL.
2. Supply a process name when testing application-based routing.
3. Enable Matching only to filter the results.
4. Inspect the matching rules, which the documentation says are highlighted in green.

Test one expected match, one unrelated destination, and one overlapping case. That small rehearsal is preferable to discovering an overenthusiastic rule during a meeting.

Let the picker handle exceptions​

The Picker menu includes Show on no rule. Enable it to choose a browser/profile whenever no rule matches; leave it disabled if unmatched links should go directly to the fallback.

The documentation also describes configurable manual invocation and toast notifications identifying the selected destination.

There is a practical balance here. Too many prompts turn automation into a questionnaire. Too many broad rules turn it into guesswork. A modest ruleset, a dependable fallback, and a picker for exceptions are a sensible starting point.

URL cleanup and Microsoft 365 links​

The project documentation provides two useful details beyond basic browser selection.

First, it says ClearURLs support was introduced in version 6.3.0 and is enabled by default. Recognized tracking elements are removed using a database bundled with Browser Tamer. This is URL cleanup, not a replacement for browser security or tracker-blocking protections.

Second, Microsoft 365 link handling has a deliberate distinction: Browser Tamer documents examining the destination inside supported Office 365 wrapped links for rule matching, while still opening the original wrapped URL for security reasons.

That matters for work links. A routing decision can consider the destination without automatically discarding the protective wrapper. URL unshortening is separate again: the developer explicitly says it requires internet access.

Firefox Containers need an additional component​

Ordinary Firefox profiles and Firefox Containers are not interchangeable routing targets.

Browser Tamer’s documentation says container routing requires enabling container support and installing Open external links in a container. Rediscover browsers afterward so configured containers can appear. Ordinary Firefox-profile routing does not carry that container-extension requirement.

If a container is missing, check that integration before rebuilding unrelated URL rules.

Troubleshooting the handoff​

When a link opens somewhere unexpected, work through the chain:

• Nothing reaches Browser Tamer: Check Windows’ default-app associations.
• The wrong profile opens: Confirm the destination profile and inspect matches in Pipeline debugger.
• The picker appears unexpectedly: Look for overlapping rules.
• A process rule fails: Test from the originating application, not a copied URL.
• Settings cannot be changed on a work PC: Ask IT whether policy controls the associations.

That last possibility is documented by Microsoft: administrators can manage app defaults through Group Policy and mobile device management. Microsoft also requires ordinary user-default changes through Windows’ system interface; registry-based changes are not supported.

Browser Tamer’s strongest use case is modest but valuable: getting an externally opened link into the browser session where it belongs. It will not tidy four browsers’ worth of tabs. It can, however, stop Windows from adding the next tab to the wrong pile.