Profiles, links and sync
Air Traffic Control
Routes for links that open from other apps, and App Links for a page's links to apps. Match a domain, a path or a local port, then open it in a space and a main window or Little Arx.
This page is a first draft. It may change before the public beta.
When you click a link in another app, Air Traffic Control decides where it opens. Set it up in Settings → Links → Air Traffic Control, a page with your routes and a tester.
Routes
Each route is two lines, checked from the top; the first route that's on and matches wins.
- URL: Domain matches that host only; Domain and Subdomains also matches hosts under it, only at a dot, so
example.comcoversdocs.example.combut notmyexample.com. Then the pattern: a host, with an optional port and path, such aslocalhost:3000orgithub.com/capturecontext. Start it withhttp://orhttps://to match only that scheme. - Open in: where the link opens.
| Open in | Where |
|---|---|
| Most Recent Space | The space of the window you used last, in any profile |
| Ask for a Destination | Nothing opens until you choose a profile; see below |
| A profile → Most Recent Space | That profile's space you used last, or its first space |
| A profile → one of its spaces | That space |
Except for Ask, a route also names the window: Main Window or Little Arx. Little Arx opens in the route's space and its profile, so its cookies and sign-ins are that profile's.
The Domain and window choices open a short list under the button. Click a choice, or use ↑ and ↓ and press ↩. Esc closes the list without changing anything.
Ask for a Destination
A route or Otherwise set to Ask for a Destination holds the link before it loads, and a small list of your profiles opens at the pointer, over whatever app you're in. Nothing is requested, no redirect runs and no tab is made in any profile until you choose; then the link opens once, in Little Arx, in that profile's most recent space. Use it for sign-in links, such as Google's, which can stop working if they start in one profile and move to another.
- The profile you used last is at the top and already selected, so ↩ opens the link there.
- ↑ and ↓ move between profiles. Type to filter by profile or space name. Each row shows the space the link will open in.
- Esc, or clicking anywhere else, closes the list and drops the link. Nothing opens.
- The list doesn't bring Arx's other windows forward.
- When several links arrive at once, the list asks about one at a time, in the order they came. Links that don't ask wait their turn.
Click a Google sign-in link in Mail. The profile list opens at the pointer with the most recent profile selected; press ↓ to Work and Return; the sign-in page opens in Little Arx in Work.
Links from other apps all go through Air Traffic Control the same way: when Arx is your default browser, from apps that open a link in Arx, and from links you drop on Arx in the Dock. Files you open with Arx (Finder's Open With, open -a, a file dropped on Arx in the Dock) have no site for a route to match, so they open where links no route matches go, Little Arx by default.
Hosts ignore case and support international domains. A path is case-sensitive and encoded, and matches as a prefix: /docs also matches /docs2. Query strings and fragments aren't matched; without a port, 80 for HTTP and 443 for HTTPS.
New Route adds an empty route at the end; it's saved once its pattern names a host. Changes save as you make them. If one can't be saved, for example a space that was deleted, the route says why. Each route has a switch to turn it off, and its right-click menu moves it up or down.
Some examples:
| URL | Open in |
|---|---|
Domain github.com/capturecontext | Work, Main Window |
Domain and Subdomains figma.com | Design → Most Recent Space, Main Window |
Domain accounts.google.com | Ask for a Destination |
Domain meet.google.com | Most Recent Space, Little Arx |
Domain localhost:3000 | Side project, Main Window |
Otherwise
Otherwise, at the end of the routes, sends every other link to a space and a window, or Ask for a Destination to choose each time. Out of the box, other links open in Little Arx in the most recent space.
App Links
Some sign-ins end in an app rather than a page: you connect a service in Claude, sign in in Arx, and the last page hands off to the app with a link such as claude://…. App Links decides what happens to those links. Set them up in Settings → Links → App Links, the page under Air Traffic Control.
New Handler adds a card. From the top:
- The app button, then Name, Scheme and the remove button. The app button shows a plus until you pick an app, then that app's icon.
- Host and Path prefix.
- The links the handler catches, such as
Catches claude://login/callback…, or the rule the scheme breaks. - Add profile, and the Enabled switch.
Click the app button to pick an app:
- Type to search. The list shows the apps macOS has for the card's scheme, then the installed apps that open links of their own, one row for each scheme an app opens. ↑ and ↓ move through the list and ↩ picks.
- Choose… picks any app on disk, such as a custom build or a copy of an app for one workspace.
- Picking an app fills in Name and Scheme, shows the app's icon, and opens the handler's links in that app. A name you wrote yourself stays.
- System Default clears the app: links open in whatever app macOS uses for the scheme.
You can also fill in the fields yourself. Scheme is the part before ://, such as claude; it starts with a letter, then letters, digits, +, - or ., and can't be http, https, file or another web scheme. Host and Path prefix are optional and narrow the handler to one host and a path prefix. A new card is saved once it has a scheme.
The first handler that's on and matches wins. Under the card come its routes, read the way link routing reads: each profile's route first, then Otherwise for every other page. Add profile adds a profile's route just above Otherwise, starting with the same handling. Each route is one of:
- Open with System Default opens the app macOS uses for the link, as other browsers do.
- Open in ‹app› opens it in the handler's app. Other App… picks a different app for just this row, for example the Work copy of Claude for the Work profile.
- Run script runs your script instead, so you decide where the link goes, for example to the one Claude window that started the sign-in.
Arx remembers where a chosen app is and follows it if you move or rename it. If it's gone when a link arrives, the prompt says so and offers Open with System Default; Arx never opens another app in its place without asking. If no app opens the link at all, the prompt says that too.
The page's profile picks the handling, so sign in from the profile that matches the app window. With Ask for a Destination you choose that profile when the sign-in link arrives.
| Handler | In Work | In Personal | Otherwise |
|---|---|---|---|
Claude, claude | Run fxclaude open-url work "$1" | Run fxclaude open-url personal "$1" | Open in Claude |
New Handler, click the plus, type cla and press Return: Name and Scheme fill in and the card shows Catches claude://…. Add profile → Work; its route appears above Otherwise. Choose Run script and press Tab to use the example.
Scripts
An empty script field shows an example, fxclaude open-url work "$1". Press ⇥ (or →) in the empty field to use it; elsewhere Tab moves on as usual. The example uses open-url, a command coming to fxClaude and fxCodex that hands the link to the Claude or Codex window for one workspace; the App Links footer links here. Until it's there, any command that takes the link as an argument works.
Under the field, Test runs the script with a sample link and Remove removes a profile's route. If the test fails, its error appears in full below.
The script runs with zsh. The link is $1; write "$1", in quotes, so it stays one argument. Arx never puts the link into the script's text, so a page can't add commands to it unless your script runs the link itself, for example with eval. The script also gets:
| Variable | Value |
|---|---|
ARX_LINK | The link, the same as $1 |
ARX_LINK_SCHEME | The handler's scheme, such as claude |
ARX_PROFILE_ID, ARX_PROFILE_NAME | The page's profile |
ARX_SOURCE_ORIGIN | The site that opened the link, such as https://claude.ai, never the full page address |
Before a script runs, Arx checks the link: it must be a link with the handler's scheme, at most 8 KB, with no line breaks or other control characters. Otherwise Arx offers to open the app instead.
A script that sends a link to another app may show a macOS Automation prompt, such as "Arx wants to control Claude". Allow it to deliver the link. You can change that permission later in System Settings → Privacy & Security → Automation.
A script gets 30 seconds; after that Arx stops it. What it prints goes to a log in ~/Library/Logs/Arx/App Links, one file per run.
The prompt
Pages can open these links on their own, through a redirect, so Arx asks first, on the page's window, in place of Chrome's Open "App"? dialog. The prompt shows the app's icon and the question, the site that asked and the link, then its buttons at the bottom, the main one last:
- Open app: Open "Claude"?, with Open Claude, named after the app you chose or the one macOS uses.
- Run script: Land in Claude Work?, with Land in Claude Work: the handler and the profile. Show Script shows what will run.
- ↩ presses the main button and esc is Cancel. The main button waits a moment before it takes a click or ↩, so input meant for the page can't run anything.
- The menu beside the main button has Copy Link, which copies the link and leaves the prompt open.
- Always allow ‹site› to open this skips the prompt next time that site opens a link for this handler. It's offered for HTTPS sites and local ones (
localhost), not plain HTTP sites. The handler lists the sites you allowed, each with Forget.
If the page moved on before you answered, nothing runs. If the script fails or runs out of time, the prompt shows its error and the end of its log, with Open ‹app› to open the app instead: the handler's app, or the one macOS uses.
Private windows never run scripts and never remember a site: they always ask, then open the app. Links no handler matches keep Chrome's own Open "App"? dialog.
In Claude's Work window, connect Linear. Sign in in Little Arx in Work; at the end the prompt says Land in Claude Work. Click it and the Work window shows Linear connected.
Test and fix
- The tester shows which route wins for a URL, and where it would open, without opening it.
- Route Current URL in the Tabs menu runs the current page through your routes, with a review sheet.
- If a destination fails, for example a space you deleted, the link waits in Incoming Links in the main window, with retry, override, copy and cancel. Links that ask also wait there when Arx can't show the profile list, as in automated runs.
Routes only apply to links from other apps and to Route Current URL, not to links you click inside Arx, redirects or Peek. App Links apply to a page's links for other apps, clicked or redirected.