Feature request: Deep link / URL scheme routing for cloned apps

[bystritskiy]

Hi!

First of all, thank you for Parall — it works really well for running multiple isolated Claude Desktop instances with different accounts.

I ran into a limitation that seems like a perfect feature for Parall.

Use case:

I have multiple Claude Desktop clones created with Parall, for example:

• Claude (Personal)
• Claude (Work)

Each clone has its own app data and its own Claude account. This part works great.

The problem appears when connecting external integrations / connectors, for example Asana. The browser completes the OAuth/integration flow and then redirects back to Claude Desktop using a deep link like:

claude://...

Since claude:// is a global macOS URL scheme, Launch Services opens whichever app is currently registered as the handler. This creates two problems:

1. The deep link may open the wrong Claude clone.
2. If another Claude instance is already running, macOS/Claude may route the link to the wrong running instance even if the default handler was changed with duti.

I tried changing the URL scheme handler manually with duti, for example:

duti -s claude

This works only partially. It works better when all Claude instances are closed, but it is unreliable when one of the Claude clones is already running. Also, Claude or macOS may re-register the default handler later, so the setting needs to be repeated.

Feature request:

Could Parall provide built-in URL scheme/deep link handling for cloned apps?

Possible UX ideas:

1. Per-clone URL scheme registration
   • Allow a clone to claim specific URL schemes, for example claude://.
2. Deep link router
   • Parall could register itself as the handler for the original URL scheme.
   • When a claude://... link arrives, Parall could ask which clone should receive it, or route it to the last active / configured clone.
   • Ideally, this could be configured per clone.
3. Temporary routing mode
   • “Route deep links to this clone for the next N minutes”
   • Useful for OAuth flows and connector setup.
4. “Always route this scheme to this clone”
   • Example: always send claude:// links to Claude (Zlata).

This would be very useful not only for Claude Desktop, but also for other apps that use OAuth callbacks or custom URL schemes.

Environment:

• macOS
• Parall-created Claude Desktop clones
• URL scheme: claude://
• Example flow: browser OAuth/integration callback from Asana or other connectors back to Claude Desktop

Thanks!