Processes (Pipelines)

The pipelines command family operates processes — ordered phases that chain flows with JSONPath data handoff and optional human approval gates. The UI calls them Processes; the RPC namespace is pipelines.* (with deprecated sdlc.* aliases).

All pipelines verbs require a running sidecar (akos serve locally, or AKOS_HEADLESS_URL for remote).

List processes

akos pipelines list
akos pipelines list --json

Inspect one process

akos pipelines show my-release-pipeline --json

Exits with code 5 when the id is not found.

List process runs

akos pipelines runs
akos pipelines runs --pipeline my-release-pipeline --limit 20 --json

Dispatch a new run

akos pipelines run my-release-pipeline

Pass initial context as JSON:

akos pipelines run my-release-pipeline \
  --ctx '{"ticketId":"ENG-4821","owner":"alice"}' \
  --idempotency-key eng-4821-2026-07-05

In CI or other non-TTY environments, mutations require explicit confirmation:

akos pipelines run my-release-pipeline --confirm --json

Resume after approval

When a phase requires human approval, the run pauses until a reviewer acts in the Inbox (or via inbox approve / hitl approve). Resume the process run from the CLI:

akos pipelines resume pipe_run_abc123 --json

Cancel an in-flight run

akos pipelines cancel pipe_run_abc123
akos pipelines cancel pipe_run_abc123 --confirm   # non-TTY

Typical operator loop

akos pipelines list
akos pipelines run quarterly-close --ctx '{"period":"2026-Q2"}' --confirm
akos pipelines runs --pipeline quarterly-close --limit 5
# … reviewer approves in Inbox …
akos pipelines resume <pipelineRunId>

Related topics

• Processes in the app — kanban board, chain view, column settings.
• Flows and Runs — single-flow execution and HITL escalations.
• Inbox — human approval tasks for gated phases.
• Concepts: Processes — data handoff and phase templates.
• Command reference — full pipelines.* table.