clawup.yaml manifest and .env.example in the current directory. Completely non-interactive — edit the YAML by hand to configure your deployment.
Usage
Two Modes
Fresh Init (no clawup.yaml)
Discovers local identity directories (subdirectories containing identity.yaml) and scaffolds a manifest with sensible defaults. If you don’t have identities yet, create one first with army-create (npx army-create).
Defaults:
- Provider: AWS
- Region: us-east-1
- Instance type: t3.medium
- Agents: discovered from local identity directories
clawup.yaml includes ${env:VAR} secret references, inline plugin config from identities, and per-agent secrets. Edit the values directly in the YAML file to match your setup.
Repair Mode (existing clawup.yaml)
When clawup.yaml already exists, init enters repair mode — a non-interactive refresh that:
- Re-fetches all agent identities (picks up upstream changes)
- Updates the secrets section with any new plugins, deps, or
requiredSecrets - Refreshes inline plugin config with latest
pluginDefaultsfrom identities - Warns about any missing template variables
- Regenerates
.env.exampleto reflect current requirements
Examples
Output
Creates (or updates) in your project directory:clawup.yaml— deployment manifest with${env:VAR}secret references.env.example— all required env var names with empty values
.clawup/ directory and .env are added to .gitignore automatically.
Next Steps
Afterinit completes:
- Edit
clawup.yaml— set your provider, region, owner info, and agents - Copy
.env.exampleto.envand fill in your secrets - Run
clawup deployto validate secrets, configure Pulumi, and deploy your agents
${env:VAR} reference system.