Rove

01 / Problem

Production raises the stakes.

MCP-native browser automation that returns structured accessibility trees instead of expensive screenshots.

02 / Method

Make the boundary explicit.

Architecture, operating assumptions, review, and failure behavior are designed before autonomous execution begins.

03 / Evidence

Require proof from the system.

Completion means the running workflow produces evidence—not merely that generated code compiles or a happy path demos.

Supervised handoff

How supervised handoff works

Operator Helm is preparing for design-partner testing; the first external session has not started.

When an authorized person needs to intervene in a supported, owned browser session, the agent pauses input and a session-bound viewer link lets that person take exclusive control. The agent remains fenced out until the person explicitly hands control back; before the agent resumes, it must receive a fresh observation of the session.

Stop or close the session to end the handoff and clean up its viewer access. This is intended for owned, non-critical workflows only. It does not bypass CAPTCHA or other anti-bot protections.