Skip to main content
For the full guide, see Mobpack.
This page is intentionally deployment-focused and CLI-heavy. Use Examples: Mobs first if you want to understand the multi-agent runtime before packaging it, and continue to Examples: WASM if your next step is browser delivery.

​
Pack a mob directory

Bundle a mob directory into a single portable .mobpack artifact containing the definition, skills, hooks, and config.

​
Sign a pack

Attach an Ed25519 signature at pack time for trust verification on deploy.
Signing embeds the public key but does not install the signer as trusted. The local commands below therefore use permissive mode; use strict only after installing that signer in the verifier’s trust configuration.

​
Inspect a pack

View the contents, metadata, and signature status of a .mobpack without deploying.

​
Validate a pack

Check structural integrity, schema conformance, and signature validity.

​
Run a pack

Invoke a .mobpack as a typed callable run. The input schema is validated before the flow starts; --prompt is sugar for --param prompt=<text>.
Use --detach to get a run id, then inspect or attach to the same run resource:

​
Trust policies

Trust policy resolution order:
  1. CLI flag: --trust-policy permissive
  2. Environment variable: RKAT_TRUST_POLICY=permissive
  3. Config file: trust.policy field
  4. Default: strict (fail closed)

​
Next step

After packaging and deploy flows, continue with Examples: WASM for the browser-target delivery path.