browser_handoff
A handoff action in the APX browser used for scenarios requiring human intervention, such as login, passwords, 2FA, or CAPTCHA. The agent initiates it and then waits for the user to complete the operation.
Timeline (last 90 days)
The APX browser tool provides a browser_handoff action for login, password, 2FA or CAPTCHA scenarios, recording a brief reason, marking the browser card as in handoff state, and waiting up to five minutes for the owner to complete the action.
Under the browser_handoff mechanism, the agent can receive only one of two answers: the owner has completed it (with the current URL), or the owner did not complete it within the time limit (the agent stops); the agent does not receive passwords, verification codes, or a stream of human interaction.
All Facts (2)
The APX browser tool provides a browser_handoff action for login, password, 2FA or CAPTCHA scenarios, recording a brief reason, marking the browser card as in handoff state, and waiting up to five minutes for the owner to complete the action.
50%UnverifiedUnder the browser_handoff mechanism, the agent can receive only one of two answers: the owner has completed it (with the current URL), or the owner did not complete it within the time limit (the agent stops); the agent does not receive passwords, verification codes, or a stream of human interaction.
50%