Sign-ins stay with you

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.

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

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.