This guide will walk you through creating your first rule and understanding how Default Tamer routes URLs.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/0xdps/default-tamer/llms.txt
Use this file to discover all available pages before exploring further.
Before starting, make sure you’ve installed Default Tamer and set it as your default browser.
Your First Rule: Route Slack Links to Chrome
Let’s create a rule that opens all links from Slack in Chrome.Select Rule Type
In the rule editor, set:
- Type: Source App
- Source App: Slack
- Target Browser: Chrome
Congratulations! You’ve created your first routing rule.
Understanding Rule Priority
This means rule order matters. Let’s see why:Example: Specific Before General
Say you want:- GitHub links from Slack → Firefox
- All other Slack links → Chrome
Rule 1: GitHub from Slack
- Type: Domain
- Domain:
github.com - Match Type: Exact
- Source App: Slack (if you want this only from Slack)
- Target Browser: Firefox
Rule Type Examples
Source App Rule
Route based on which app sent the link. Use case: Open all links from Cursor in Chrome- Type: Source App
- Source App: Cursor
- Target Browser: Chrome
Domain Rule (Exact)
Route based on exact domain match. Use case: Open all GitHub links in Firefox- Type: Domain
- Domain:
github.com - Match Type: Exact
- Target Browser: Firefox
Exact matching normalizes
www. prefixes, so github.com matches both github.com and www.github.com.Domain Rule (Suffix)
Route based on domain suffix. Use case: Open all Atlassian products (Jira, Confluence) in Chrome- Type: Domain
- Domain:
.atlassian.net - Match Type: Suffix
- Target Browser: Chrome
mycompany.atlassian.netjira.atlassian.net- Any subdomain ending in
.atlassian.net
Domain Rule (Contains)
Route based on domain substring. Use case: Open any domain containing “jira” in Chrome- Type: Domain
- Domain:
jira - Match Type: Contains
- Target Browser: Chrome
jira.mycompany.comcompany-jira.commyjirainstance.net
URL Pattern Rule (Contains)
Route based on URL content. Use case: Open all admin pages in Safari- Type: URL Pattern
- URL Contains:
/admin - Target Browser: Safari
/admin in the path.
URL Pattern Rule (Regex)
Route based on advanced pattern matching. Use case: Open all staging/preview environments in Firefox- Type: URL Pattern
- URL Regex:
https?://.*\.(staging|preview)\..* - Target Browser: Firefox
https://app.staging.company.comhttp://site.preview.dev
Option Key Override
No matter what rules you have configured, you can always manually choose a browser:Private Mode
Each rule can optionally open links in private/incognito mode. Use case: Open all social media links in private mode- Type: Domain
- Domain:
twitter.com - Match Type: Exact
- Target Browser: Safari
- Open in Private Mode: ✅ Enabled
Private mode support varies by browser. Most modern browsers (Safari, Chrome, Firefox, Arc) support it.
Activity Log
To see which rules are matching and debug your routing:Enable Activity Log
- Click the Default Tamer menu bar icon
- Go to ⚙️ Preferences → General
- Under Diagnostics, toggle on “Activity Log”
Activity logs are stored locally and URLs are sanitized to remove tokens, API keys, and secrets.
Disable Routing Temporarily
To temporarily disable Default Tamer without changing your system default browser:- Click the Default Tamer menu bar icon
- Toggle the switch at the top from green (enabled) to gray (disabled)
Common Patterns
Here are some popular routing setups:Work vs Personal
Development Environments
Source-Based Routing
What’s Next?
Rule Types
Learn about rule types, matching logic, and advanced patterns
Creating Rules
Step-by-step guide to building powerful routing rules
Import & Export
Back up and share your rules as JSON or CSV
Troubleshooting
Common issues and solutions