Operate

Once your agent is deployed to Zero Runtime Cloud, you operate it with the zeroruntime CLI. Run every command from inside your project folder.

I want to…	Commands	Guide
Roll out, inspect, or roll back a release	`zeroruntime up`, `zeroruntime version`	Version Management
Add or rotate provider keys	`zeroruntime up --env`, `zeroruntime secrets`	Secrets Management
Start, list, or stop conversations, or read logs	`zeroruntime invoke`, `zeroruntime session`, `zeroruntime logs`	Sessions & Logs
Take the agent offline	`zeroruntime down`, `zeroruntime version deactivate`	Scaling Down

These commands apply only to Zero Runtime Cloud. If you self-host, use your own platform instead.

How the CLI tracks state

The CLI stores your deployment’s IDs in zeroruntime.yaml so you don’t have to repeat them. Each command fills in the values it produces. You rarely edit this file by hand.

zeroruntime.yaml

version: "1.0"
agent:
  id: ag_xxxxxxxx          # set by `zeroruntime init`
  name: my-agent
build:
  image: my-agent:v0.3     # set by `zeroruntime up`; the next build is v0.4
deploy:
  id: dep_xxxxxxxx         # set by `zeroruntime init`
  version: vr_xxxxxxxx     # set by `zeroruntime up`
secrets:
  env: my-secrets          # set by `zeroruntime up --env` / `zeroruntime secrets create`

Each command finds a value in this order:

The flag you pass on the command line.
The matching field in zeroruntime.yaml, such as agent.id or build.image.
A built-in default. If there is none, the command tells you what’s missing.

Overview

Build

Plugins

Deploy

How the CLI tracks state

​How the CLI tracks state

How the CLI tracks state