openclaw tasks is equivalent to openclaw tasks list.
See Background Tasks for the lifecycle and delivery
model, and its tasks audit section for full finding descriptions.
Usage
Root Options
| Flag | Description |
|---|---|
--json | Output JSON. |
--runtime <name> | Filter by kind: subagent, acp, cron, or cli. |
--status <name> | Filter by status: queued, running, succeeded, failed, timed_out, cancelled, or lost. |
Subcommands
list
show
notify
cancel
audit
cleanupAfter are warnings;
expired or unstamped lost tasks are errors.
--code accepts task codes (stale_queued, stale_running, lost,
delivery_failed, missing_cleanup, inconsistent_timestamps) and Task
Flow codes (restore_failed, stale_waiting, stale_blocked,
cancel_stuck, missing_linked_tasks, blocked_task_missing). See
Background Tasks for severity and trigger detail per
code.
maintenance
lost, so completed cron runs do not become
false audit errors just because the in-memory Gateway runtime state is gone.
Offline CLI audit is not authoritative for the Gateway’s process-local cron
active-job set. CLI tasks with a run id/source id are marked lost when
their live Gateway run context is gone, even if an old child-session row
remains.
When applied, maintenance also prunes cron:<jobId>:run:<uuid> session
registry rows older than 7 days while preserving currently running cron
jobs and leaving non-cron session rows untouched.
flow
flow list --status accepts queued, running, waiting, blocked,
succeeded, failed, cancelled, or lost.