Question 1

How do I set up Finicky to automatically open work sites in one browser and personal sites in another?

Accepted Answer

Create a configuration file at ~/.finicky.js with handlers for different domains. For example, define rules to match work domains and route them to Chrome, and personal domains to Firefox, using the match and browser properties as shown in the basic configuration. Test it by setting Finicky as your default browser and opening links from various applications.

Question 2

Finicky or Browserosaurus: which is better for macOS browser switching?

Accepted Answer

Finicky is ideal for automated, rule-based routing with code configuration, while Browserosaurus offers a graphical prompt for manual selection. Use Finicky for automation and Browserosaurus for ad-hoc choices; they can work together as mentioned in the README, but Finicky requires more technical setup.

Question 3

Can Finicky remove UTM parameters from URLs before opening?

Accepted Answer

Yes, Finicky supports URL rewriting to strip tracking parameters like UTM. In your configuration, use the rewrite array with a match for URLs containing UTM parameters and a function to modify the URL object, similar to the example for redirecting x.com to xcancel.com. This helps clean up URLs automatically.

Question 4

How to debug Finicky when it's not opening the right browser?

Accepted Answer

Start Finicky manually to open the configuration/troubleshooting window, which provides logs and error messages. Check the configuration file for syntax errors, ensure rules are correctly matched using the wiki documentation, and consider testing with simple rules first to isolate issues.

Question 5

Does Finicky work with all browsers on macOS, including Safari?

Accepted Answer

Finicky can handle multiple browsers and apps that support URL handling, including Safari. The configuration allows specifying browser names like 'Safari' or 'Google Chrome', but compatibility depends on the app's ability to receive URLs from Finicky via macOS system integration.

Question 6

What are the performance implications of using Finicky as a default browser?

Accepted Answer

Acting as a default browser adds a layer of processing for URL routing and rewriting, which might introduce minimal latency. However, for most users, the overhead is negligible compared to the benefits of automated organization, as rules are processed locally on macOS.

Finicky

What is Finicky?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions