Assistants and MCP
Grants and approvals
Grant by capability, not all or nothing. Choose the context, the access classes and when Arx asks before a change.
This page is a first draft. It may change before the public beta.
Every client has three settings in Settings → Advanced → Local assistants (MCP): which context it can see, which access classes it holds, and when Arx asks before a change. Reading tabs, taking screenshots, reading pages and clicking on them are separate permissions, and each assistant sees only the tools its grant covers.
Arx's own assistant is listed here too, as Arx Assistant with the profile's name, one per profile you allowed it in. It follows the same grants and approvals.
Context
Permitted context is a list of profiles, spaces and tabs.
- A profile grant covers all of its spaces, folders, tabs and Favorites, including spaces created later.
- A space grant covers its folders and tabs.
- Favorites otherwise need their own tab grants.
- Private windows are never exposed.
Some classes only work with whole-profile grants: history, downloads, extensions, and managing spaces and profiles.
Allow the focused tab shortcut lets the assistant say “the focused tab” instead of naming one: it passes "focused" as both targetID and expectedRevision. Arx picks the tab you're looking at in the focused window when the tool runs (in Split View, the focused pane's), only if your grant covers it, and tells the assistant which tab it used.
Access classes
Each client's access is a list of switches grouped under What it can see, What it can do and Developer, below the context it may use. Hover a switch, or ask VoiceOver, for what it allows; the table has the same.
| Setting in Arx | Class | What it allows |
|---|---|---|
| Read browser organization | read | Lists the granted spaces, folders and tabs with sanitized URLs, and waits for pages to finish loading. Every other class also needs this one. |
| Allow page screenshots | screenshots | Viewport, region, element and full-page screenshots. They include visible page content and embedded frames. |
| Read page text and semantic elements | pageContent | Bounded text and semantic snapshots of permitted pages, PDF export and PDF text. Form values and password subtrees are left out. |
| Interact with pages | interact | Clicks, typing, text replacement, option selection, key presses, scrolling, hovering, dragging, page dialogs and media controls. Needs page content too. |
| Organize tabs and folders | organize | Opens, navigates, moves, pins, renames and closes tabs and folders, opens Peek and Little Arx, manages Split View and restores archived tabs. |
| Manage profiles, spaces and settings | browserAdmin | Creates, renames, reorders and deletes spaces and profiles, and sets their appearance. Reads and changes listed settings, Air Traffic Control rules, search and keyboard shortcuts, and extensions. Security settings and assistant access are never included. Profiles, spaces and extensions need a whole-profile grant; deleting a profile erases its browsing data. |
| Search browsing history | history | Searches visited pages of whole-profile grants. URLs drop query and fragment; titles can still be private. |
| See and control downloads | downloads | Lists downloads of whole-profile grants, starts new ones, cancels them and shows finished files in Finder. Private downloads never appear. |
| Upload files | files | Answers file choosers a page opens with files from your Mac. Every upload still asks you, showing each file. |
| Run scripts in pages | script | Runs JavaScript in granted tabs, in a separate world that can't read cookies, passwords, card numbers or saved credentials. A script can still do anything you can do on that site. Needs developer mode. See browser_evaluate. |
| Read console and network logs | devtools | Keeps the console messages and finished requests of a granted tab once the assistant asks, without headers, cookies or bodies. Needs developer mode. See browser_logs. |
| Request details | networkDetails | On top of console and network logs: each request's headers and bodies, and a HAR export. Cookie, Authorization and other credential headers never leave Arx, and credential fields in form and JSON bodies are hidden. Needs developer mode. |
| Allow sign-in requests | signIn | The assistant can ask you to sign in. See Sign-ins stay with you. |
Run scripts in pages, Read console and network logs and Request details are off for every client, and you can turn them on only while developer mode is on. If you turn developer mode off, Arx refuses them until you turn it on again.
There is no class for reading the clipboard, reading saved passwords or touching the file system, and no tool for them.
When Arx asks
Ask before changes is a standing choice that survives restarts. Arx decides how risky each action is, never the assistant. Reading never asks.
| Setting | Policy | What happens |
|---|---|---|
| Every time | alwaysAsk | Every change waits for you, unless you allow scoped commands for 15 minutes. |
| Only for closing or removing | destructiveOnly | Changes run. Closing tabs, deleting folders, spaces, profiles and saved entries still ask. |
| Never | never | Only the presses below that pay, send, post or delete ask. The grant stands until you change it. |
When a change needs approval, Arx shows Assistant requests a browser change with the action, its target and any warning, and you choose Allow once or Decline. Allow scoped commands for 15 minutes gives a temporary pass; Require approval again ends it early.
While Arx waits for you
The assistant's request waits for your answer, and the assistant hears at once what Arx is asking, so it can tell you in its own chat: Waiting for the user to approve a click in Arx.
- Claude Code shows this under the running tool and waits up to 10 minutes. When you answer, the request finishes and the assistant carries on.
- Other assistants hear it after about 15 seconds, since some end a tool call within a minute. They're told to pass the question on and, once you've answered, to ask Arx again for the same request.
Either way the request stays open in Arx for 15 minutes. If you approve after the assistant stopped waiting, the change runs once, and the assistant collects its result by asking again. Asking again never repeats a change. If you don't answer within 15 minutes, the request ends and the prompt goes away. The same applies to an extension install waiting in the Extensions sheet's review.
These ask every time, whatever the policy:
- Uploading files. Arx shows every path.
- Accepting a page dialog or permission request, including any text sent to a prompt.
- Allowing a site a permission in site settings (camera, microphone, location, notifications or the clipboard).
- Installing an extension. Instead of the request above, the profile's Extensions sheet shows the same review as Add to Arx, naming the assistant. See Extensions.
- A press that pays, sends, posts or deletes on a website. The request names what will be pressed and the site, for example Presses “Place order” and This may pay or place an order on shop.example. A 15-minute pass doesn't cover it.
What counts as paying, sending, posting or deleting
Arx decides from the page the assistant read, not from what the assistant says. It looks for the way people label a last step, so Send and Pay now ask and Sending options doesn't:
- What it clicks. A button or menu item whose short label starts with Pay, Buy, Place order, Donate, Send, Post, Publish, Delete, Empty Trash, Transfer, Cancel subscription and the like, in English and several other languages. Clicking an icon inside such a button counts as pressing it. A link that goes somewhere never asks, whatever it says.
- Card forms. Whatever sends a form with a card number or security code field pays, however it's labeled, Continue and Next included.
- What Enter submits. Pressing Enter or typing a line break in a field asks when any of its form's buttons would. Outside a form, only a nearby Send counts, as in a chat box, so a filter box beside a Delete never asks. When the assistant read only part of a long page and the form runs past it, Enter asks too. Enter or Space on such a button asks too.
- Clicks at a point. A click at a spot on the page asks whenever the page shows such a control, or the assistant read only part of a long page, since a scroll may have moved one under that spot. A drag that starts or ends on such a control asks too. Clicks on an element the assistant picked from the page ask only for that element and what's inside it.
- Scripts. A script (
browser_evaluate) that clicks, submits a form, dispatches events or sends data asks, whatever the policy. Scripts that only read follow the policy.
A label never makes a press safe; it can only make Arx ask. While an assistant runs unattended, nobody can answer, so such a press fails with userActionRequired.
Starting a download and running a script ask every time under Every time, even while scoped commands are allowed for 15 minutes, and neither can be part of a batch. A script's request shows its full text. Under Only for closing or removing or Never they run without asking, like other changes, unless a script clicks, submits or sends.
A batch of up to 16 steps asks once for the whole list: One approval covers exactly these steps, in this order. A batch with a step that pays, sends, posts or deletes asks whatever the policy, and marks that step.
When an assistant is working
While an assistant changes a page (clicks, types, scrolls, answers a dialog, controls media, runs a script, or uses a tab command), the page shows a pill at the top: Claude Code is controlling this page, with the client's name, and Stop. Its row in the sidebar shows a small badge too. Both stay a few seconds after the last action, so a run of quick steps reads as one. An assistant that only reads a page shows nothing.
Stop ends what the assistant is doing and pauses its access (a tab where it ran a script reloads, since that's the only way to end what the script left running): every request then fails with paused, and a temporary 15-minute pass ends. The pill turns into … is stopped with Resume until it fades. You can also Pause and Resume a client in Settings → Advanced → Local assistants (MCP), where a paused client shows Paused. Pausing keeps its grant as it was, and lasts until you resume it, after quitting too.
Tabs an assistant opens
Arx is testing a way to keep track of the tabs assistants open and tidy them away. It's on in the beta:
- An assistant always opens a new tab in the background. It never takes over one of yours, and the tab you're on stays selected.
- The tab's row shows a small sparkle. Rest the pointer on it to see which assistant opened it, such as Claude Code opened this tab.
- When the assistant comes back to the same page in a later run, it uses the tab it left there instead of opening another beside it.
- A tab nothing has used for 15 minutes goes to the archive, where you can reopen it. Time your Mac spends asleep doesn't count. Change the delay, or choose Never, under Agent tabs in Settings → Advanced → Local assistants (MCP).
A tab stays while it's on screen or selected in its space, while an assistant is working in it, or when something is typed into a form on it, and for good once you pin or rename it. A tab you click in the sidebar, or one you choose Keep Tab for in its right-click menu, is yours from then on: it loses the sparkle, the assistant can't take it over, and it's never tidied.
To turn it off, turn off its feature flag in Settings → Advanced → Feature Flags and relaunch Arx, or quit Arx and run:
defaults write dev.capturecontext.arx ARX_AGENT_TABS -string off
To turn it back on, turn the flag back on in the same place, or quit Arx and run:
defaults delete dev.capturecontext.arx ARX_AGENT_TABS
Activity
Recent activity lists operation names and outcomes, up to 128 entries for the current app session. Page text, typed text and field values are never logged.