Run Spinup Agents

Runtime commands use an agent runtime key (sk_agent_...) scoped to one agent ID. Use SPINUP_API_KEY for a one-off command or store the key in CLI config if this machine should use that runtime key by default.

Check status

SPINUP_API_KEY=sk_agent_... spinup agents status agent_01hxyz...

JSON output:

SPINUP_API_KEY=sk_agent_... spinup agents status agent_01hxyz... --json

Execute a prompt

SPINUP_API_KEY=sk_agent_... spinup agents exec agent_01hxyz... \
  --input "Summarize this repository." \
  --harness openclaw \
  --timeout-seconds 45 \
  --workspace workspace \
  --cwd repo

Supported exec flags:

• --input: prompt text to run
• --harness: openclaw or hermes
• --timeout-seconds: positive integer timeout
• --session-id: continue a prior harness session
• --workspace: safe relative runtime workspace path
• --cwd: safe relative runtime working directory

Use --json when another tool should parse the output:

SPINUP_API_KEY=sk_agent_... spinup agents exec agent_01hxyz... --input "Run the task" --json

List runs

SPINUP_API_KEY=sk_agent_... spinup agents runs list agent_01hxyz...

Use pagination flags when needed:

SPINUP_API_KEY=sk_agent_... spinup agents runs list agent_01hxyz... --limit 20 --cursor "v1:..."

Get one run

SPINUP_API_KEY=sk_agent_... spinup agents runs get agent_01hxyz... run_01hxyz...

Run history returns support-safe fields only. It includes lifecycle timestamps, harness selection, request options, final output, generic error state, warnings, usage counts, and bounded evidence counts. It does not return the original prompt input, raw stdout/stderr, raw provider payloads, billing cost details, audit events, actor IDs, internal session IDs, Worker Host IDs, microVM IDs, or secret/env maps.