status, terminal, step_count, result, and error. Use it for a point-in-time check - for waiting, use phone_task_monitor instead of polling this in a loop.
Read-only: it never changes task state.
Parameters
string
required
The task to inspect.
boolean
Include the task’s recorded steps (screenshots, thinking) in the payload.
integer
Return only steps newer than this step number.
Response
string
One of four states:
string
Set when
status is completed. See the
terminal outcomes table.integer
Number of steps recorded so far.
string
The task’s answer, when it completed with
terminal: "ok".object
Present on tasks that ended in error or need input. On a
needs_user_control task, error.control_type and error.prompt describe
what the phone needs.This task-level
error object is part of the status payload. It is
distinct from the JSON-RPC error envelope, which appears only when a
tool call itself fails.Related
phone_task_monitor- the right tool for waiting- Task lifecycle - states and outcomes in depth