mirror of
https://github.com/OpenRouterTeam/spawn.git
synced 2026-04-28 03:49:31 +00:00
Agents running on spawned VMs couldn't delete child spawns because `spawn delete` requires an interactive terminal for the picker UI. Added --name and --yes flags: when both are provided in non-interactive mode, the server matching the name is deleted without prompts. This enables agents to manage their own child VMs programmatically. Updated all skill files to teach agents the headless delete syntax. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: A <258483684+la14-1@users.noreply.github.com>
896 B
896 B
Spawn — Create Child VMs
You have the spawn CLI installed. Use it to provision cloud VMs with AI agents.
Usage
spawn <agent> <cloud> --headless --output json --prompt "task description"
Agents: claude, codex, openclaw, zeroclaw, opencode, kilocode, hermes, junie
Clouds: hetzner, digitalocean, aws, gcp, sprite
Example
spawn claude hetzner --headless --output json --prompt "Implement the auth module"
Returns JSON: {"status":"success","ip_address":"...","ssh_user":"root","server_id":"..."}
Managing Children
spawn list --json— see running childrenspawn delete --name <name> --yes— tear down a child VMspawn tree— see the full spawn tree
Context
- You are running inside a spawned VM (SPAWN_DEPTH is set)
- Cloud credentials are pre-configured — no auth prompts
- OpenRouter billing is shared with the parent