Skip to main content
Deprecated — the legacy orchestration runtime. It keeps working. This page documents a command group that drives the frozen legacy runtime (also called: orchestration, warm pool, instance pool, Hermes, sidecar, container runtime, hosted runtime, runtime.pool). It keeps working for existing configs and accepts no new capabilities. Nothing here is disabled, refused or gated, and no route or CLI command on this page has been removed.Since 2026-08 each command on this page also prints a one-line banner on stderr and attaches a machine-readable deprecation object to the JSON envelope on stdout, which stays JSON.parse-able. There is no sunset date: the surface is frozen, not scheduled for removal.New work declares a team({ lead, agents }) on runtime.durable() and submits work with naive teams submit. The per-subcommand replacement is in the table directly below.

Replacement

naive tasks drives the legacy orchestration runtime’s board, which is frozen. Three subcommands have no replacement, and the reason is recorded rather than left implicit: The banner id is dep.tasks.
For a tenant still on the legacy (hermes) runtime, naive teams submit answers 501 not_configurednaive tasks create remains the working way to put work on that board, which is why this page is deprecated rather than removed.

Overview

How It Works

Tasks are the unit of work in the naive kanban system. The CEO creates objectives, which are broken into tasks, which are assigned to employees. Tasks flow through statuses: pendingin_progresscompleted (or blocked). The embedded kanban dispatcher in the Hermes gateway automatically spawns worker processes for assigned tasks every 15 seconds. Workers call kanban_complete() when done.

List Tasks

Options


Create a Task

Options

The title is a positional argument (no --title flag needed). Task IDs can be either standard UUIDs or Hermes task IDs (e.g., t_a2a1ae0c) — both formats are accepted by all task commands.

Complete a Task

Options


Block / Unblock

Blocked tasks are surfaced to the CEO for resolution or re-assignment.

Add a Comment

Comments create an activity trail visible to all agents and the CEO.

Run a Task

Directly trigger a worker to start executing a specific assigned task. The task must already have an assignee.
This triggers the kanban dispatcher to immediately spawn a worker for the specified task. Use it when you want to start work on a task without waiting for the periodic auto-dispatch.
The task must be assigned to an employee and not be in done or blocked status. If unassigned, use naive tasks create with --assignee or PATCH the task first.

Dispatch Tasks

Auto-assign pending tasks to available employees based on skills and capacity.

Board Statistics

Returns task counts by status, employee utilization, and blocked task summary.

Typical Workflow