Troubleshooting
First: run OIOXO Doctor
Tools menu → “Run health check.” Doctor verifies the things OIOXO depends on — WebGPU, the in-browser Node sandbox, Python and SQLite runtimes, local storage — and tells you which (if any) failed and what that limits. Re-run after changing browsers or flags.
Browser support
| Browser | What works |
|---|---|
| Chrome / Edge / Brave (desktop) | Everything — on-device model, live preview, terminal, local folders. |
| Firefox / Safari | Editing and scaffolding; live preview, terminal, and local folders need Chromium. BYOK works. |
| Mobile | Light use; the desktop app or a desktop browser is the real experience. |
Common issues
“The on-device model hit a GPU/memory error and stopped”
The model’s runtime ran out of GPU memory or the driver reset — it’s the runtime, not your project. Try again, close other GPU-heavy tabs and apps, or switch to your own API key (same loop, no local GPU). If it recurs, a smaller model tier is the stable choice on that machine.
“The model didn’t write any code”
The task likely exceeds what the small on-device tier can plan — especially on CPU. Make the request more specific and smaller, or use a BYOK key for frontier-size tasks.
The build seems stuck
The narration line tells you what’s happening — a first build includes the one-time model download, and slower devices show “(slower on this device — still working).” If the timer keeps rising with no progress for minutes, reload and try again; the project recovers from its last snapshot.
No live preview
Live preview needs a Chromium browser. Doctor will show exactly which runtime is missing. Static sites still preview instantly everywhere via the built-in renderer.
“You’re out of build tokens for now”
The free allowance refills automatically — the message shows the reset time. No action needed; Pro removes the wait entirely.
A new version is available
When a newer OIOXO is deployed, a quiet banner offers Refresh. Your work is snapshotted locally, so refreshing is safe.
Still stuck?
Check the FAQ, or write to support@oioxo.com with what Doctor reported and the last lines of the build log.