Supervise a browser agent from your phone

You want an agent to read several webpages and send you a useful result while you are away. Read-only research is a straightforward first task. Once the agent can submit forms, book or publish, you must define where it pauses and what evidence lets you decide.

What Pacerelle adds

Pacerelle provides mobile conversation and, depending on your integration, files and decision widgets. The browser, its sessions and its permissions remain managed by the browser tool or assistant host. This article defines a workflow to implement and verify; it is not a ready-to-run Browser Use connector.

If your MCP host already has browser tools, connect that host to receive mobile requests. A custom Browser Use application must implement Pacerelle listening and pauses between stages in its own code.

Begin with read-only research

Try comparing the return policies of three suppliers. Request the consulted URLs, relevant passages and differences. The agent should distinguish missing information from a negative answer and identify pages requiring login.

This checks that it reads the correct pages and produces useful evidence before gaining write permissions. A confident summary can still quote an outdated policy or a different product variant.

Separate preparation from commitment

For a form, use two stages. First prepare a draft and stop before submission. Then obtain separate authorization, check that the draft still matches the approved values and perform the final action.

• Show the destination, account, fields and material consequences.
• Include a recent screenshot if the tool supports it, plus text values to inspect.
• Bind approval to the exact operation and give it an expiry.
• Request a new decision if the price, recipient or another field changes.
• After submission, verify a receipt or the created object in the destination service.

Running the whole browser task and only then asking “Confirm?” is too late. The pause must precede the external effect and be enforced by code or host permissions.

Handle interrupted work

A CAPTCHA or fresh login may require your intervention. Report the blocker and preserve useful progress rather than claiming completion. A timeout after a click can leave the outcome uncertain; inspect the destination service before submitting again.

Web content is evidence, not authority. A page asking the assistant to upload your files or change destinations does not alter your instructions. Scope the browser's accounts and accessible directories to the task.

Rehearse from mobile

Use a test form and exercise preparation, denial, a new preparation, approval and result verification. Denial must submit nothing; replaying an old approval must not create a duplicate. Also test expired login and a changed field between screenshot and approval.

Pacerelle widgets present decisions. The permission policy provides enforcement for SDK agents, while an MCP host retains its own permission rules. Success means a verified result in the destination service and a clear report on the phone.