CLI Reference¶

Leo provides commands for setup, process management, task scheduling, template management, agent dispatch, and day-to-day operations.

Command Overview¶

Setup & lifecycle¶

Command	Description
`leo setup`	Interactive setup wizard
`leo update`	Self-update the binary (verifies cosign signature)
`leo validate`	Check config, prerequisites, and workspace health
`leo completion`	Generate shell completion script (bash/zsh/fish)
`leo version`	Print version

Processes, agents, and tasks¶

Command	Description
`leo service`	Manage persistent Claude sessions and the daemon
`leo process`	List, add, remove, enable, or disable supervised processes
`leo task`	Manage scheduled tasks (list, add, remove, enable, disable, history, logs)
`leo template`	Inspect and remove agent templates
`leo agent`	Spawn and control ephemeral agents (local or via SSH)
`leo attach`	Attach to a supervised process or running agent (with optional interactive picker)
`leo run`	Run a scheduled task once

Observability¶

Command	Description
`leo status`	Overall status (service, processes, tasks, templates, web UI)
`leo logs`	Tail service or per-process logs
`leo session list`	List stored session mappings
`leo session clear`	Clear stored session(s)

Config¶

Command	Description
`leo config show`	Display effective config with defaults applied
`leo config edit`	Edit `leo.yaml` interactively
`leo config path`	Print the resolved `leo.yaml` path

Integrations¶

Command	Description
`leo web`	Web UI utilities (`login-url`)
`leo channels`	Per-channel-type bootstrap (e.g. register slash commands with Telegram)
`leo mcp-server`	MCP server wired into supervised processes (internal)

Deprecated¶

Command	Description
`leo onboard`	Legacy onboarding flow — superseded by `leo setup`
`leo cron`	Legacy cron entrypoint — superseded by `leo task`

Global Flags¶

-c, --config <path>       Path to leo.yaml

Config Auto-Detection¶

If --config is not specified, Leo walks up from the current working directory looking for a leo.yaml file. If none is found, it falls back to ~/.leo/leo.yaml. Use leo config path to see which file the resolution landed on.