Runs
Every message that requires work becomes a run:POST /api/agents/runs and
GET /api/agents/runs/{id}.
It asks questions
When your instruction is ambiguous, the agent pauses and asks instead of guessing. That is a feature: a lead search that guesses wrongly about your ICP spends real credits producing the wrong list. In the dashboard, answer in the chat. Headlessly:1
Poll the run
GET /api/agents/runs/{id} returns status: "paused" and the question in
result_summary.2
Answer it
POST /api/agents/runs/{id}/reply with { "message": "…" } resumes the
same run mid-thought — no new run, no lost context."interrupt": true to stop a still-working run and immediately start a new
one with your message.
Cancelling
POST /api/agents/runs/{id}/cancel stops a
run right away. Cancellation is authoritative, not advisory — the run is marked
cancelled immediately, so a wedged executor cannot keep it “running” forever and
occupying one of your parallel-run slots.
What the agent can do
Playbooks and sources
A run can be pointed at specific inputs and behaviours:Conversations, folders and brands
Runs hang off conversations, which are scoped to your workspace and narrowed to the brand you are working in.?brand=all widens a listing to every brand in
the workspace — useful for agencies — but never past the workspace.
Organise conversations into folders from the sidebar.
Parallel runs
Pro and Business also get the full-size model with configurable reasoning
effort; lower tiers run on the lighter models.
Skills
Save an instruction set as a reusable, selectable playbook.
