/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:
- Command-line flag
- Explicit
--configfile ./.swarm/swarm.yaml./swarm.yaml- User-global
$XDG_CONFIG_HOME/swarm/swarm.yaml - Built-in default
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 forkre-executes a whole run from an event point viarun.fork. - Conversation.
swarm forkchat(above) forks one agent conversation into a sandbox viaconversation.fork. - Single event.
swarm event replayandswarm agent replayredeliver an event to its subscribers.
--bundle-hash differing from the source’s bundle) are gated separately
and currently rejected. See Fork and replay.
