Works locally, 500s in production
Server log: `Error: OPENAI_API_KEY is undefined` — yet it works on your machine.
Try it in a safe space, coached, before it counts for real. Break things freely — everything here is simulated, so nothing real can break — and let Messy coach you toward the fix instead of handing it over.
Practice runs entirely on authored, in-memory scenarios. No real API keys, databases, deployments, or third-party accounts are ever touched — so you can break things freely and nothing real can break.
Pick a broken setup and work it out. Stuck? Messy escalates help one step at a time — a gentle nudge, then the underlying concept, then the specific area, and only at the end a full walkthrough. It never just hands you the graded answer.
Every builder ships bugs, breaks a deploy, and leaks a key at least once. Here you meet those messes on purpose — read the symptom, diagnose the real cause, and choose the fix. Stuck? The hints escalate one nudge at a time, and solving with fewer of them earns more.
Server log: `Error: OPENAI_API_KEY is undefined` — yet it works on your machine.
The deploy log ends with "Build completed" but the browser console shows 404s for every `/assets/*.js` file.
A secret scanner flags `const key = "sk-live-..."` committed to your public repo.
`SyntaxError: Unexpected token` — the model wrapped its JSON in ```json fences.
`fetch failed: 503 Service Unavailable` bubbles up and crashes the UI.
`429 Too Many Requests` from the model provider.
Every environment returns `401 Unauthorized` from the provider at once, right after you rotated the compromised key.