A person, in the loop when it matters.
Full autonomy is the wrong default for anything consequential, and full manual defeats the point. The useful middle is a run that knows when to ask.
- No credit card required
- Free plan to start
Why unattended automation fails
- A login or challenge ends the whole job.
- Some actions genuinely need a person's approval.
- Restarting from scratch wastes everything already done.
- Nobody can see what the automation was looking at.
How hand-off works
Live takeover
A person can drive the same browser, live, and the run resumes from exactly there.
Approval as a mode
`confirm_actions` parks the run before anything that changes state, rather than relying on prompt wording.
It says why it stopped
The run reports the reason — a challenge, a login, an approval — so you can route it to the right person.
No lost work
Resuming continues the same run rather than starting over.
How you'd call it
A goal and a schema over HTTP — no selectors to maintain and no browser fleet to run.
“Set config approval to confirm_actions, watch the run's live view, and take the wheel when it pauses.”
Questions people ask
Can my users take over, not just my team?
Yes — the live view and takeover are available through the API, so you can surface them in your own product.
What if nobody responds?
The run times out and reports why, rather than hanging indefinitely. Scheduled agents refuse an approval mode that could park forever, by design.
Does taking over break the run?
No — that's the point. Browza finishes the action it was on, hands over, and picks up wherever you leave it.
Related use cases
What will you hand over?
Start with one task. Watch it run, take the wheel whenever you want, and keep the ones that earn their place.