Browse documentation

Follow a task list

Use the CLI's filtered task stream and understand NDJSON updates.

rp task list --follow uses the project task-follow endpoint with x-repopack-task-follow-version: 2. The server sends the current filtered snapshot and then task changes.

Human output prints the first baseline using normal task-list formatting. JSON output is NDJSON: the first record is a snapshot, followed by enter, update, leave, or non-sensitive control records. Reconnect baselines are reconciled without printing the initial snapshot again. A task that leaves the selected result is emitted as a removal, so clients do not retain stale rows.

The server applies normal API authentication, project selection, visibility, filters, and ordering before delivery. Following a list never broadens access.

An unsupported or missing follow version receives HTTP 426 with rp update guidance. The CLI reports it once and does not enter its reconnect loop. A current CLI can consume the older unscoped snapshot contract, but an old server cannot enforce owner filtering; the CLI warns and follows the unfiltered list. Upgrade the server before relying on owner-scoped automation.

This compatibility behavior is specific to task-list follow. It is not a general minimum-CLI policy for unrelated API routes.