BrowserChooser

How to Build a Custom BrowserChooser for Seamless Web Navigation

Managing multiple web browsers is a necessity for modern workflows. Developers test code across different engines, power users separate work and personal accounts, and privacy advocates isolate specific tasks.

Relying on a single default browser often leads to friction, like manually copying links or opening the wrong profile. A custom BrowserChooser solves this by acting as a lightweight intermediary. When you click a link, it intercept the request and routes it to the correct browser based on rules you define. Here is how to build your own custom BrowserChooser. Understanding the Architecture

A custom browser chooser does not render web pages. It functions as a routing utility registered to the operating system.

[ Click Link in App ] │ ▼ [ Your Custom BrowserChooser ] ──( Evaluates Rules ) │ ├─► Matches “work.com” ──► Open in Work Browser (e.g., Chrome) └─► Matches “bank.com” ──► Open in Secure Browser (e.g., Brave) The system relies on three core mechanisms:

OS Registration: The system must recognize your application as a valid web browser handler.

Argument Parsing: The application must accept the URL as a command-line argument.

Process Spawning: The application launches the target browser executable with the URL. Step 1: Writing the Routing Logic

You can build this tool using any language that compiles to an executable or runs via a script interpreter. Below is a Python implementation utilizing the native subprocess and sys modules.

import sys import subprocess import re # Define paths to your browser executables BROWSERS = { “chrome_work”: “C:\Program Files\Google\Chrome\Application\chrome.exe”, “firefox_personal”: “C:\Program Files\Mozilla Firefox\firefox.exe”, “brave_secure”: “C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe” } def route_url(url): # Rule 1: Send work domains to Google Chrome if “internalworksite.com” in url or “://company.com” in url: launch_browser(BROWSERS[“chrome_work”], url) # Rule 2: Send financial institutions to Brave elif re.search(r”(paypal|bank|crypto).com”, url): launch_browser(BROWSERS[“brave_secure”], url) # Default: Everything else goes to Firefox else: launch_browser(BROWSERS[“firefox_personal”], url) def launch_browser(browser_path, url): try: subprocess.Popen([browser_path, url]) except Exception as e: print(f”Error launching browser: {e}“) if name == “main”: # Ensure a URL argument was passed by the OS if len(sys.argv) > 1: target_url = sys.argv[1] route_url(target_url) Use code with caution. Step 2: Registering the App with the Operating System

To make the script selectable as a default browser, the operating system must know it handles the http and https protocols. On Windows (via Registry)

Save your Python script as an executable (using tools like PyInstaller) or create a batch file wrapper. Then, add keys to the Windows Registry to register the application. Open regedit.

Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet.

Create a new key for your application (e.g., CustomChooser).

Set up the capabilities and association keys pointing to your executable path.

Alternatively, use a community tool like Default Programs Editor to easily assign your script to handle the HTTP/HTTPS protocols without manual registry editing. On macOS (via App Bundle)

macOS requires an application bundle with a properly configured Info.plist file.

Package your script into an .app bundle using py2app or native Automator.

Edit the Info.plist inside the bundle to include the CFBundleURLTypes:

CFBundleURLTypes CFBundleURLSchemes http https Use code with caution.

Move the application to the /Applications folder to trigger system registration. Step 3: Setting the Default Browser

Once registered, configure your OS to route all traffic through your new utility.

Windows: Open Settings > Apps > Default Apps. Select Web Browser and choose your custom application.

macOS: Open System Settings > Desktop & Dock. Find the Default web browser dropdown and select your custom app. Advanced Enhancements

A basic router works well, but you can expand the utility as your workflow evolves:

Interactive UI Override: If a link does not match any predefined rule, have the script launch a tiny GUI window (using Tkinter or PyQT) offering a click-to-select grid of your available browsers.

Profile Isolation: Instead of just switching browsers, pass specific flags (like –profile-directory=“Profile 2” for Chromium) to open links directly in specific user profiles.

Logging and Analytics: Add a lightweight logging function to track which domains you visit most frequently, helping you optimize your routing rules over time. Conclusion

Building a custom BrowserChooser eliminates the daily friction of cross-browser friction. By taking control of the system-level link routing, you can design a fluid environment where the right web tools open automatically for the right tasks.

If you want to tailor this browser routing tool to your exact workflow, tell me: What operating system do you use?

Which browsers and specific profiles do you want to connect?

What routing rules (like specific keywords, domains, or work vs. personal use) do you need?

I can provide the exact code and setup instructions for your environment.