Human handoff

Hand off to a person, then resume automation

Pause automation at sign-in confirmations, approvals, QR codes, or other manual checkpoints, let a person complete the step through Remote View in the same Session, and then resume automatically.

Example · pause for a human action and resume in the same Session

Integration options

Prerequisite:
Fetch and fully execute the official Lexmount Setup Prompt returned by https://browser.lexmount.cn/api/agent-setup/browser-cli.
Continue only after installation, authentication, and environment validation all pass; otherwise stop and report the failure truthfully.

Task:
Use browser-cli only to create one temporary Lexmount Cloud Browser Session and open https://docs.python.org/3/. Confirm that the "Tutorial" and "Library reference" entries are visible, then hand control to the user through Remote View so they can choose which section to open.

Execution:
1. Pause automation after confirming that both entries are visible, and provide the current Session's Remote View to the user.
2. The user only needs to click "Tutorial" or "Library reference" and does not need to reply in the chat.
3. Keep the same Session active until the manual action is complete. The Agent must not choose on the user's behalf or create another Session to conceal the handoff.
4. Detect the user's selection, resume automatically in the same Session, and inspect the final URL and main heading again.
5. Close the Session.

Acceptance:
For "Tutorial," the final pathname must be /3/tutorial/index.html and the main heading must contain "The Python Tutorial." For "Library reference," the final pathname must be /3/library/index.html and the main heading must contain "The Python Standard Library." Automation must resume in the same Session. If the main task succeeds but cleanup fails, report partial success.

Cleanup:
On success, failure, timeout, or cancellation, close only the Session created by this task. Never close a pre-existing Session.

Return:
Report only the status, selected documentation section, initial and final URLs, same-Session resume result, elapsed time, cleanup result, and sanitized error summary. Except for the Remote View used during handoff, do not expose API keys, Project IDs, Session IDs, connect URLs, or WebSocket URLs.

Integration options

Prerequisite:
Fetch and fully execute the official Lexmount Setup Prompt returned by https://browser.lexmount.cn/api/agent-setup/browser-cli.
Continue only after installation, authentication, and environment validation all pass; otherwise stop and report the failure truthfully.

Task:
Use browser-cli only to create one temporary Lexmount Cloud Browser Session and open https://docs.python.org/3/. Confirm that the "Tutorial" and "Library reference" entries are visible, then hand control to the user through Remote View so they can choose which section to open.

Execution:
1. Pause automation after confirming that both entries are visible, and provide the current Session's Remote View to the user.
2. The user only needs to click "Tutorial" or "Library reference" and does not need to reply in the chat.
3. Keep the same Session active until the manual action is complete. The Agent must not choose on the user's behalf or create another Session to conceal the handoff.
4. Detect the user's selection, resume automatically in the same Session, and inspect the final URL and main heading again.
5. Close the Session.

Acceptance:
For "Tutorial," the final pathname must be /3/tutorial/index.html and the main heading must contain "The Python Tutorial." For "Library reference," the final pathname must be /3/library/index.html and the main heading must contain "The Python Standard Library." Automation must resume in the same Session. If the main task succeeds but cleanup fails, report partial success.

Cleanup:
On success, failure, timeout, or cancellation, close only the Session created by this task. Never close a pre-existing Session.

Return:
Report only the status, selected documentation section, initial and final URLs, same-Session resume result, elapsed time, cleanup result, and sanitized error summary. Except for the Remote View used during handoff, do not expose API keys, Project IDs, Session IDs, connect URLs, or WebSocket URLs.