Troubleshooting
When Studio gets stuck, and how to unstick it.
Agent loops on the same error
It's trying the same fix repeatedly and failing.
- Roll back the last few turns.
- Rephrase the problem with more specifics or paste the exact error message.
- Try a stronger model (Settings → Model → Frontier) for one turn, then switch back.
Preview doesn't update
The dev server inside the workspace might have crashed.
- Click the Restart preview button.
- Check the output panel for an error (port conflict, build error).
- If restart doesn't help, roll back one turn.
"Out of memory" in the workspace
Studio sandboxes have RAM limits. Heavy builds (big webpack
configs, huge node_modules) can OOM.
- Ask the agent to prune deps, or pick a smaller framework.
- For projects too big for the sandbox, deploy them and continue development locally.
Streaming stops mid-turn
Usually a network hiccup between you and Suzko. The agent's state is server-side, so it didn't lose its turn. Refresh — pending work finishes; you'll see the result.
"You've hit your monthly spend cap"
Studio billing stopped you to prevent surprises.
- Settings → Spend Cap → raise it.
- Or wait until next month — the cap resets.
- Free tier projects (3 starter projects) don't accept spend caps; they're already capped at the free allowance.
File edits look right but app behaves wrong
Sometimes the agent edits the wrong file (monorepo confusion, or two files with similar names).
- Use the diff view (Versions → Diff) to verify.
- Be specific in next prompt: "in
src/lib/auth.ts, not inapps/admin/auth.ts".
Generated code doesn't compile
- Paste the compile error verbatim.
- The agent reads the file before re-editing, so it'll match the current state.
"Something went wrong" toast
Usually a transient error from a model provider. Retry the last turn. If it persists, switch models (Sonnet → Haiku or vice versa) to route around any provider-side hiccup.
When to bail to your editor
If you've spent 10 turns fighting the agent on something, deploy what you have and finish in your editor. Studio is brilliant at scaffolding and rapid iteration; sometimes a stubborn bug needs you sitting at the keyboard.