Skip to main content
Every command that reads or changes runtime state calls the v1 API at /v1/rpc or /v1/ws. The one exception is swarm verify, which validates contract files on disk and needs no running runtime.

Global flags

Resolution precedence, highest first:
  1. Command-line flag
  2. Explicit --config file
  3. ./.swarm/swarm.yaml
  4. ./swarm.yaml
  5. User-global $XDG_CONFIG_HOME/swarm/swarm.yaml
  6. Built-in default
(The Configuration page lists the same layers.) Environment variables are not an accepted configuration source — retired SWARM_* variables fail with a teaching error naming the flag or config key. See Configuration.

Runtime

swarm run start without --connect boots a runtime in-process; with --connect <url> it drives a running one. It takes --event <name>, --payload <file>, and --data <dir>.

Runs

Events and entities

Agents and conversations

Control and diagnostics

Bundles

Persisted contract bundles in the runtime store, identified by canonical bundle hash (a content hash of the bundle’s files).

Exit codes

Three replay surfaces, at different granularities:
  • Run. swarm run fork re-executes a whole run from an event point via run.fork.
  • Conversation. swarm forkchat (above) forks one agent conversation into a sandbox via conversation.fork.
  • Single event. swarm event replay and swarm agent replay redeliver an event to its subscribers.
Cross-bundle run forks (--bundle-hash differing from the source’s bundle) are gated separately and currently rejected. See Fork and replay.