Skip to main content
Use a human checkpoint for approvals, payments, complex authentication, or reviewing work before the agent continues. The run’s browser.ready event contains a live_view_url. After the first turn stops at a safe checkpoint, open that URL, let the human interact, then send a follow-up with the same session ID.
The browser is kept alive for follow-ups when possible. If it has expired, V4 restores the conversation and workspace but provisions a new browser, so complete the human step before the live browser’s timeout.
Treat live-view URLs as credentials. Anyone with the URL can interact with the browser while it is active.
See Get run events for the event response.