World cookbook
Runnable recipes, each an outcome against twins with real SDKs, fake keys and local state. Consult the model for shared state semantics and the CLI reference for current commands. A recipe that needs a real service or a checkout of another repository says so on its page.
Start with a complete application
Copy a starter with volter example <name> --dir <empty-folder>, install its exact dependencies, review its detected vendors, then run it inside a World. The source stays with your app; no private application checkout or platform account is required.
| Example | What you can do |
|---|---|
| Customer onboarding | Create a customer, store SQL application state, send a welcome email, inspect a bounce or refusal, and resume a partial signup; browser form included |
| Workplace handoff | Give an agent ordinary company context, link a GitHub issue to a Linear ticket, report it to Slack, and retry a refused notification |
| Baseline and integration | Start two workers from shared data and deliver selected changesets to a separate integration World |
Demo a workflow reuses the onboarding app rather than asking you to invent another demo. These pages describe their source workflows; their exact dependencies do not establish an executed walk. Execution claims require their own retained evidence.
Start with a small example
These recipes use exact published packages and require no private source checkout or platform account. Use one in an empty directory. Each page names its prerequisites, assertions and limits.
| Recipe | Outcome | Prerequisites |
|---|---|---|
| Browser signup and signed webhooks | Create an account, persist its session, inspect vendor data, verify a callback and sign out | Node 22.6+, npm; Chromium for the automated suite |
| Hosted Checkout and the customer portal | Decline and retry a payment, start a trial, manage cancellation and replace a card through vendor pages | Node 22.6+, npm; Stripe 3.0.3+ with hosted-page support and World browser creation |
| Repeatable data and behavior | Create a record, assert a one-time fault, retry a scripted answer, reset and repeat | Node 22.6+, npm |
| Isolated CI workers | Run two independent jobs and stop each World after success or failure | Node 22.6+, npm; package registry during preparation |
| Transactional email | Send with Resend's SDK, inspect a local sign-in code and resume the same message | Node 22.6+, npm |
| AI messages and streaming | Consume a labeled local response through Anthropic's unchanged SDK and stream | Node 22.6+, npm |
| Run a tool and stream its result | Consume a scripted OpenAI tool call, create a GitHub issue through its SDK and stream the confirmation | Node 22.6+, npm |
| Users and sessions | Create a user, verify a session token, revoke and resume its stored state | Node and npm |
| Redis data and quotas | Store a customer, consume a fixed-window quota, resume it and advance to the next window | Node and npm; pinned Upstash SDKs |
| Object storage | Upload and read a file with the real S3 SDK, then resume the same stored object | Node 22.6+, npm; Cloudflare R2 scope |
| Managed app database | Obtain a local Supabase database connection, store a record and read it after resume | Node 22.6+, npm; PostgreSQL-wire scope |
Tutorials teach a task step by step; cookbook recipes assemble reusable workflows. Getting started is the first local lesson. Manual adoption, recovery and coverage explain how to adapt a recipe to your app.
Larger application case studies live in the source repository and name their own checkout prerequisites. This site serves the complete starter examples above.