Skip to main content
Hand a longer, multi-step browser task to an agent, then keep working while it runs, checking in when you want rather than waiting on it.

​
Setup

Connect the MCP server first, see setup.

​
What you’ll do

  • Submit a task with outcrawl_agent
  • Check its status separately, it does not block
  • Read what it has produced once it has something

​
Example exchange

“Find three vendors that ship the part I described and get me their pricing pages.” The assistant calls outcrawl_agent with the task and a budget. It gets an id back in milliseconds, the run itself can take minutes, so the assistant should check status rather than treat the id as a failure. A little later, “how is that going?” calls outcrawl_agent_status, and once it is done, outcrawl_agent_results returns what it found.

​
What it can’t do

Once submitted, no tool call can redirect the task mid-run. outcrawl_agent_control steps in by taking the browser yourself, and when the run stops to ask something only you know, outcrawl_agent_answer answers it and the run carries on.