What changed

Browser Use 1.0.7 removes the hard 60-second failure for MCP calls. browser_exec returns partial output around 50 seconds while the cell continues running, and callers can poll the same execution with an empty code request.

Why it matters

Long browser tasks can now survive client time limits without forcing duplicate execution, reducing accidental repeated writes and ambiguous task state.

What to do

Pin 1.0.7 in a disposable browser profile, run a task longer than 60 seconds, poll it to completion and verify idempotency, cancellation, partial-output ordering and no repeated external action.

Caveat

The project release establishes intended behavior, not independent exactly-once guarantees. Callers still need explicit task identity, cancellation and reconciliation around state-changing browser actions.