> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pomerado.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Hand off to a person

> Pause a job so a person finishes a step in its browser, then let it continue.

A hand-off pauses a job at a step a person should do or check, such as reviewing a form before it's submitted. The person finishes the step in the job's own browser, on a protected Pomerado page, and the job continues.

## Ask for one in a build request

A tool hands off only where its build request asks. Set `browser_handoff` to `true`, and say in `task` exactly where a person should review or act:

> Fill the claim form, then let me check it before it's submitted.

While it builds, the tool tries the step once: the build waits with `status` `needs_input` and a `browser_handoff` question. Open its page from the build in the Dashboard or from `answer_url`, and finish it as a run's hand-off. A build with `browser_handoff` runs on a browser with a live view, so a `pomerado-browser-vendor` header naming one without it is refused with `invalid_request`.

To make the step optional, ask for a yes-or-no input named for it, such as `review_before_submit`, so each run can skip it.

Pomerado keeps human steps to a minimum. It never hands off for a CAPTCHA, and it signs in by itself unless the build request asks a person to.

## Send the person the page

When a run reaches the step, the job reads `status` `needs_input`, and its `input_request` holds one question of type `browser_handoff`. Send the person the request's `answer_url`. It opens the job's live browser beside what to do and the inputs the step lists.

The job's owner can open it, and so can anyone on its Business team. On a Personal account, only the owner can.

## Finish or stop

The person works in the browser, then chooses one:

* **Mark as done**: the job continues from the page as the person left it.
* **Stop job**: the job ends now and won't finish its task. The page asks to confirm first.

A hand-off waits at most 30 minutes. Unfinished by then, the job fails with `no_response`.

> [accordion] Details
>
> * `answer_job` and `POST /v1/jobs/{id}/answers` can't answer a hand-off. They refuse it and say a person finishes it at `answer_url`. MCP's `get_job` tells your agent to send the person that link.
> * A tool with a hand-off runs in a browser from the start, never as its HTTP version.
> * While the person works, the browser opens the tool's own website and the sites it's known to use. Before it opens any other site over https, it asks the person, who chooses **Allow** or **Don't allow**. An allowed site stays allowed until the hand-off ends. A plain http address, or one with a username or password in it, is still refused without asking.
> * After Mark as done, the tool checks the page. If it isn't where the step should leave it, the job fails with `handoff_state_changed`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.