Manage Spinup Agents

Use these commands for basic control-plane management of a Spinup Agent. They call the same public /v1 API as the SDK.

Create an agent

spinup agents create "Support Agent"

Creation saves a draft-only agent. It does not start runtime capacity and cannot run until you deploy it.

Use JSON output when scripting:

spinup agents create "Support Agent" --json

Deploy an agent

Deploy promotes the current draft configuration into the active release used by future runs, schedules, and Agent Chat. It does not start runtime capacity by itself.

spinup agents deploy support-agent

Use JSON output when scripting:

spinup agents deploy support-agent --json

Update an agent

Use spinup agents update to change the agent name, primary model, runtime sizing, or package-install policy in one call:

spinup agents update support-agent \
  --name "Support Agent v2" \
  --model openrouter/anthropic/claude-sonnet-4-5 \
  --max-output-tokens 64000 \
  --memory-mib 8192 \
  --disk-gib 10 \
  --install-mode curated

The --model value uses <provider>/<model>, so OpenRouter model names keep their own slash after the provider. --max-output-tokens caps one model response and defaults to 64000 when omitted. Supported public runtime sizes are 4096, 8192, or 16384 MiB of memory and 4 or 10 GiB of disk.

Updates save draft configuration. Future runs keep using the active release until you run spinup agents deploy <agent>.

To change only the response cap while keeping the current provider and model:

spinup agents update support-agent --max-output-tokens 32000

Rename an agent

Rename by ID:

spinup agents rename agent_01hxyz... --name "Support Agent v2"

Rename by slug:

spinup agents rename support-agent --name "Support Agent v2"

Control-plane agent commands treat values starting with agent_ as IDs and other values as slugs. The agent slug may change after a rename. Use the returned slug for later commands.

Renames save draft configuration. Deploy after the rename when future runs, schedules, and Agent Chat should use the new active release.

Delete an agent

Delete by ID:

spinup agents delete agent_01hxyz... --confirm support-agent

Delete by slug:

spinup agents delete support-agent --confirm support-agent

The confirmation value must match the current agent slug. If the agent has a ready environment, deletion first follows the same teardown path used by the dashboard. If an environment lifecycle operation is already in progress, deletion is rejected and you can retry later.