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 cron schedules work on the frozen legacy runtime.
naive cron pause has no replacement: the durable runtime has no pause. Stop the team, or
unschedule. The banner id is dep.cron.
naive cron the CLI is deprecated. /v1/cron/* the URL prefix is not.That prefix has two unrelated tenants. Nine of its routes are platform reconcilers invoked
by the scheduler with a shared secret, not by you: drain-events, reconcile-connections,
reconcile-billing, reconcile-agent-profiles, reconcile-deliveries,
reconcile-deployments, verify-domains, charge-phone-rentals and process-conversions.
None of them is deprecated, none carries a deprecation header, and none is affected by anything
on this page. If you are looking at a /v1/cron/… request in a log, check which of the two it
is before concluding anything.
Overview
How It Works
Cron jobs are managed through the Hermes gateway’s native Jobs API (/api/jobs). Each firing sends a prompt to the CEO, which creates tasks and dispatches them to employees. This enables automated recurring workflows like weekly reports, daily email checks, or scheduled social media content.
Create a Cron Job
Options
Output
List Cron Jobs
Returns all cron jobs with:
- ID, name, schedule (cron expression)
- Status (active, paused)
- Prompt that fires on each run
- Last run timestamp and result
- Next scheduled run time
Trigger Manually
Fires the job immediately, regardless of schedule. The regular schedule is not affected.
Pause a Job
The job remains configured but will not fire on schedule. You can still trigger it manually with naive cron trigger.
Remove a Job
Permanently deletes the cron job. Past executions remain in history. Cannot be undone.
Typical Workflow