Assistants and MCP

Sign-ins stay with you

When a site needs you to sign in, the assistant hands the page to you. Every assistant pauses, and none of them sees what you type.

This page is a first draft. It may change before the public beta.

When a site asks for a password, the assistant hands the page to you. Every assistant pauses while you sign in, and none of them sees what you type. Arx tells the assistant whether you finished, never what you typed.

An assistant asks you to sign in: Arx names the exact site, pauses every assistant while you type, and asks before handing the tab back, with the assistant's access kept.

Turn it on

The assistant needs Allow sign-in requests (signIn). With it, the assistant can only ask. You approve in Arx.

What you see

  1. The assistant calls browser_sign_in with action: "begin", the tab, and the page's exact origin. Arx shows Assistant requests your sign-in, with who asked and the exact origin, including its port.
  2. Pause assistants and continue pauses every assistant's reads and actions, in every tab and profile. Don't type a password or code until Arx says assistants are paused.
  3. Sign in yourself. If you navigate away, the handoff is cancelled and privacy stays locked.
  4. I confirm this session is signed in records your confirmation. Arx doesn't check the sign-in itself.
  5. End privacy lock finishes. Every assistant disconnects when the lock ends. Under Keep access, pick the ones that may reconnect with the same access and expiry; the others must be authorized again.

If an earlier assistant action on the same page has no confirmed result, the handoff is blocked until that page navigates or closes.

What the assistant gets

The handoff call waits while you approve and sign in, telling the assistant what's happening, so it doesn't have to keep asking. If it stops waiting first (after 10 minutes in Claude Code, 15 seconds elsewhere), it follows the handoff again with action: "status".

Only states, through action: "status" with the same operationID: approvalRequired, securingPrivacy, userActionRequired (you are signing in), userConfirmed, cancelled, expired or blocked. No passwords, one-time codes, cookies, account names or tokens are accepted or returned. An operation expires after five minutes, and action: "cancel" ends it.

While the lock is on, every other tool and client is denied, including inventory, page reads and screenshots. Headless runs can't sign in, because nobody is there to approve.

Signing in with a saved password

When you've saved a password for a site, an assistant can ask Arx to sign in with it. Arx fills the password into the page and submits the form itself. The assistant never sees the password or the account name. It only learns whether signing in worked.

An assistant signs in with a saved password only after you approve: the prompt names the site and the account, and can let it sign in to that site without asking next time.
  1. The assistant calls browser_password_sign_in with the tab and the page's exact origin. It needs Allow sign-in requests (signIn).
  2. Arx asks you first, in the same approval card as other assistant actions, and shows the site and account. If you've saved more than one account for the site, pick one. Arx only uses passwords saved in that tab's profile for that exact site: the same scheme, host and port.
  3. Approve, and Arx fills and submits the form.

To skip the question next time, turn on Let agents sign in to … without asking before you approve. That covers this site in this profile only, and only when you've saved one account for it. To take it back, remove the site under Sign-in without asking in Arx's assistant settings, or in the profile's Passwords list in Settings.

The assistant gets one of three outcomes, with a short reason:

  • signedIn: Arx submitted the form, and the site stopped asking for a password.
  • needsUser: only you can go on. Maybe the site asks for a one-time code, macOS asks you to confirm first, nobody approved, or there's more than one account and nobody picked. The assistant then hands the page to you with browser_sign_in.
  • failed: maybe nothing is saved for this site, the page has no sign-in form, the site refused the password, or the page changed before Arx could submit.

If Arx filled a password and the page still shows a password field, the assistant can't capture, read or act on that page until it navigates. Some pages have a "show password" button, and this keeps a screenshot from revealing your password. Private windows have no saved passwords, so an assistant can't sign in there this way.

Planned
Signing in with Apple Passwords or another password manager, and with passkeys. Passkeys depend on Apple approving passkey support for Arx.