Demos
Each demo runs locally with Docker. No LLM API keys required — all tools and models are mocked.
Runaway Agent Demo
A support agent with a quality-loop bug burns ~$10 in 12 seconds without Cycles — auto-terminated only because the demo enforces a safety timeout. In production, there would be no timeout. With Cycles, the agent stops cleanly at $1.00.
What it shows: Budget enforcement stops a cost runaway before damage accumulates.
Mechanism: reserve → deny → no downstream call
Run it
git clone https://github.com/runcycles/cycles-runaway-demo.git
cd cycles-runaway-demo
docker compose up --buildThe demo provisions its own tenant and budget automatically. Watch the terminal output — you'll see the unguarded agent overspend, then the guarded agent stop at the $1.00 limit.
About the recording
The recording above uses an accelerated call rate (~$10 in 12 seconds) for visual punch. Running ./demo.sh yourself produces ~$5.95 over 30 seconds at realistic LLM call latency — same enforcement behavior, more realistic pace.
View on GitHub · Blog walkthrough
Action Authority Demo
A support agent handles a billing dispute in four steps. Cycles allows internal actions (notes, CRM updates) but blocks the customer email — before it executes.
What it shows: Toolset-scoped budgets give agents authority over safe actions while blocking risky ones.
Mechanism: decide → DENY → no email send
Run it
git clone https://github.com/runcycles/cycles-agent-action-authority-demo.git
cd cycles-agent-action-authority-demo
./demo.shThe script starts the full stack (Redis, Cycles Server, Admin Server), provisions a tenant with action-scoped budgets, and runs the agent in both unguarded and guarded modes. No API keys required — all LLM calls are mocked.
View on GitHub · Blog walkthrough
Next: wire Cycles into your app with the End-to-End Tutorial, compare it to your current stack, or — if you're new to the category — read What is Cycles?.