Problem:
Firefox now supports multiple profiles, which is great for separating contexts (work, personal, testing, client accounts, etc.). But there's no way to control which profile a link opens in when it's clicked from outside the currently active profile window — whether that link comes from a terminal, an email client, a chat app, an IDE, or another program entirely.
In practice, this means:
What should be one action — clicking a link — becomes: switch profile → confirm the right window is focused → go back to the source → click/paste the link → verify it landed correctly. Repeated across a normal day of switching between contexts, this adds up to real, constant friction, and undermines the reason for using separate profiles in the first place.
Containers solve a related problem within a single profile, but profiles offer stronger isolation (separate extensions, logins, storage, everything) — and there's currently no equivalent routing mechanism for them.
Requested feature:
Allow users to define pattern-matching rules (regex or glob) that determine which profile a link should open in — conceptually similar to how Multi-Account Containers routes URLs into containers, but targeting profiles instead. For example:
*.corp-domain.com/* → Profile: Work github.com/myorg/* → Profile: Work * → Profile: Default
This needs to work regardless of where the link originates — an external app via the OS default-browser handler. Only links clicked inside Firefox itself should open in the current profile.
Why it matters:
Without this, using multiple profiles for genuine isolation is significantly less convenient than it should be — every single link requires manual profile identification and window switching, which defeats much of the productivity benefit profiles are meant to provide.