Skip to main content
The operator command doubles as the runtime server and a CLI for inspecting and managing state. Subcommands run standalone (no running service required).

​
Usage

operator                   # start the runtime
operator <subcommand>      # run a CLI command

​
Agent Resolution

CLI commands that need an agent name resolve it in order:
  1. --agent flag
  2. OPERATOR_AGENT environment variable
  3. Default agent from config
In job hook scripts, OPERATOR_AGENT is set automatically.

​
Setup

operator init              # scaffold ~/.operator/ with starter config and agent
Creates the directory structure, operator.yaml, SYSTEM.md, and a default AGENT.md. Safe to run multiple times — existing files are not overwritten.

​
Inspection Commands

operator config            # print resolved configuration as JSON
operator agents            # list configured agents with transport and model info
operator skills            # list discovered skills with env status

​
Log Viewing

operator logs [-f/--follow] [-n/--lines N]
Tails ~/.operator/logs/operator.log. Defaults to the last 50 lines.