task

Task Queue Management

Interact with the rp1 persistent task queue. Tasks are stored in ~/.rp1/rp1.db and processed in FIFO order (oldest first). The task system is a queue and state tracker -- execution is the responsibility of the agent or harness hook that picks up the task.

Task Lifecycle

Tasks move through these states:

pending -> in_progress -> completed
                       -> failed
pending -> cancelled
in_progress -> cancelled

• New tasks start as pending.
• pickup atomically transitions the oldest pending task to in_progress.
• Only in_progress tasks can be completed or failed.
• Only pending and in_progress tasks can be cancelled.

Operations

Create a Task

Queue a new task for later execution.

rp1 agent-tools task create \
  --type <type> \
  --description <text> \
  [--payload <json>] \
  [--project <path>]

Option	Required	Description
--type	Yes	Free-form task type (e.g., check-annotations, archive-feature, remediate-audit)
--description	Yes	Human-readable description of the work
--payload	No	JSON string with type-specific data
--project	No	Absolute project path for scoping (omit for global tasks)

Example:

rp1 agent-tools task create \
  --type "check-annotations" \
  --description "Review open annotations from last audit" \
  --project /Users/dev/myapp

Example with payload:

rp1 agent-tools task create \
  --type "remediate-audit-findings" \
  --description "Fix security issues found in auth module" \
  --payload '{"files":["src/auth.ts","src/session.ts"],"severity":"high"}'

List Tasks

View tasks filtered by status and/or project.

rp1 agent-tools task list \
  [--status <status>] \
  [--project <path>] \
  [--limit <n>]

Option	Required	Description
--status	No	Filter by status: pending, in_progress, completed, failed, cancelled
--project	No	Filter by absolute project path
--limit	No	Maximum number of tasks to return