Tonight, AI that runs all week. Every night stands on its own.
How you do anything is how you do everything.

AI ExchangeBuilding Phoenix's AI community, together. Workuity hosts tonight, and we present Founder Weekend side by side.
Sunday: five dinners from saved ingredients.
Nothing is emailed until they approve.
Each step retries. Emails send exactly once.
Approve sends one email
No answer in 2 days expires
Every run visible
Five dinners, typed output
→Email an approval link
→Up to two days, no compute
→The plan, exactly once
claudeWhat happens if they never approve?
youAfter two days, expire it.
claudeWhich steps have side effects?
✓ WORKFLOW.md: 9 steps, 1 hook, 1 sleep
Interview me about the Sunday plan, then write WORKFLOW.md as numbered steps, waits and retry rules. Wait for my OK.
Nitro: modules: ["workflow/nitro"].
It reads the docs for your installed version.
next.config, tsconfig plugin, a workflows folder.
A hello workflow with one step and one sleep.
I add the workflow skill. Then npm i workflow, wrap next.config, and prove it with a hello workflow I can watch in npx workflow web.
workflow-sdk.dev
✓ loadPantry · 9 ingredients
✓ generateWeek · 5 dinners, schema valid
✓ savePlan · status pending
claudeRun it for your test user and open the timeline.
Build loadPantry, generateWeek (AI SDK with Output.object through AI Gateway) and savePlan as steps, then run it once.
Set retries, use RetryableError for rate limits and FatalError for bad input, make side effects idempotent, then force one failure to watch it retry.
⏸ Waiting on hook plan:8f2c · up to 2 days
you[ taps Approve on the plans page ]
✓ sendPlan · ✓ markSent
Pause on a hook, email an approval link, race it against sleep("2d"), resume from an authenticated route, then send the plan once.✓ vercel.json: 0 16 * * 0 (9am Phoenix)
✓ /api/cron/sunday-plan checks CRON_SECRET
claude12 opted in · 12 runs started · 0 duplicates
A protected cron route starts one run per opted-in user each Sunday at 9 AM Phoenix time, skips duplicates, then deploy.
sundayPlan · user 41 · completed · 2 retries
sundayPlan · user 57 · waiting on hook
sundayPlan · user 63 · expired
List runs locally and on Vercel, make them findable by user and week, write a short RUNBOOK.md, and check Done when.
Also in the series: Part 9, Lock It Down. Security before anyone gets an admin console.
✗ readPhoto · 429 rate limited · retry in 1m
✓ readPhoto · eggs, spinach, feta, onion
✓ findDinners · 3 dinners
Turn Snap your fridge into a workflow: a retrying vision step, then the dinner step, with status polling and photos kept out of the run log.
An Arizona AI hackathon. Teams of 1-4.
See the hackathon ↗