Troubleshooting
First: run OIOXO Doctor
Tools menu → “Run health check.” Doctor checks the things OIOXO needs — your browser’s graphics, the built-in Node, Python, SQL, PHP and Lua runners, and local storage — and tells you which (if any) failed and what that limits. Run it again after switching browsers or settings.
Browser support
| Browser | What works |
|---|---|
| Chrome / Edge / Brave (desktop) | Everything — the on-device model, live preview, terminal, local folders. |
| Firefox / Safari | Editing and starting projects; live preview, terminal, and local folders need Chromium. Your own key works. |
| Mobile | Light use; the desktop app or a desktop browser is the real experience. |
Common issues
“The model ran out of graphics memory and stopped”
The model ran out of graphics memory or your graphics driver reset — that’s your machine, not your project. Try again, close other heavy tabs and apps, or switch to your own API key (same approach, no local graphics). If it keeps happening, a smaller model tier is the steady choice on that machine.
“The model didn’t write any code”
The task is probably bigger than the small on-device model can handle — especially without a graphics card. Make the request smaller and more specific, or use your own key for the heaviest jobs.
The build seems stuck
The status 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 comes back 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 time for now”
The free allowance refills on its own — the message shows when. Nothing to do; 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.