Cancel task
Request a task cancel (202): stamp the durable cancel flag; the worker that owns the sprite performs the sprite stop + terminal write + claim release + token revoke on its next pass. Loads the task org-scoped and checks its Space first. Idempotent — cancelling an already-terminal task replays its stored row. Needs no browser provider (the worker owns the sprite + the proxy token).
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Task id (task_<uuid>)
Response
The task, with cancel requested
A task as returned on the /v1 surface.
dev_<uuid> of the owning device.
task_<uuid>.
Discriminator for polymorphic SDK decoders. Always "task".
Why the task ended, as recorded when it was finalized: {"error": …, "detail": …} on a
failure, the agent's answer on a success. null while still running.
This is on the wire because the alternative was observed and is indefensible: a task that
reports status: "failed" and nothing else. The reason already existed in the record —
finalize_terminal writes it — and withholding it from the caller left them with a failure
they could not act on, or even describe. Details here are fixed, non-leaking strings; the
underlying transport error is logged and never persisted.