sandboxes

Standby & resume

Pause a sandbox to snapshot; resume later without a full cold create.

Create (warm pool / from-template) and resume (load snapshot) are different clocks. Do not market them interchangeably. Topology remains nested.

API

# standby
curl -fsS -X POST "$FYSTASH_API/v1/rooms/$ROOM/sandboxes/$AGENT/standby" \
  -H "Authorization: Bearer $FYSTASH_API_KEY"

# resume
curl -fsS -X POST "$FYSTASH_API/v1/rooms/$ROOM/sandboxes/$AGENT/resume" \
  -H "Authorization: Bearer $FYSTASH_API_KEY"

Auto-standby

Idle sandboxes may auto-standby after a configured idle timeout on the control plane. Resume before exec if the sandbox was paused.

Guidance

• Use standby when keeping a room warm between bursts
• Use destroy when the work is done (credits stop burning)
• Always check usage — standby/resume still consume product capacity rules