Settings
Connections, agent behaviour and rehearsal defaults. Stored in data/settings.json and used by every new run.
Connections
Connections are shown where live runs are enabled and you have access. Credentials are provisioned by Stripe Projects and never shown here.
Agent
Tried in order. If one is unavailable, the next answers. One per line.
Each failed attempt is fed back to the agent. 1–5.
Rehearsal defaults
Stripe Test Clocks advance month by month. 2–24; 13 crosses an annual renewal.
Prefilled on the Rehearsal page.
1–6 types. Each gets its own Test Clock.
Read-only here. Settings change where live runs are enabled and you have access.
Guardrails
Fixed by design. They are not settings.
Isolated sandbox
Agent code runs in a fresh CreateOS micro-VM, never on this machine.
Network allowlist
Sandboxes can reach api.stripe.com only.
Scoped writes
Migrations may only change the rehearsal's own subscriptions and schedules.
Code screening
Scripts that open other connections, read secrets or spawn processes are refused before they run.
Test mode only
Live Stripe keys are refused.
Human approval
Applying a verified migration to real customers is never automatic.