How OIOXO works
OIOXO is a chat-first IDE. You talk to a model, the model edits a real folder, and you review every change before you keep it. What makes it different is where the model runs: on your device by default, on your own API key only when you choose.
Three places a model can run
| Tier | Where | What it needs |
|---|---|---|
| Browser, CPU | A WebAssembly engine in a web worker in your tab. | Any 64-bit Chrome, Edge or Firefox. Slowest; a first turn can take minutes. |
| Browser, GPU | The same engine using WebGPU. | A browser with WebGPU on (Chrome and Edge on most machines). Several times faster than CPU. |
| Desktop, native | A native llama.cpp engine the desktop app downloads on first use. | Windows with an NVIDIA GPU (CUDA). The fastest tier by a wide margin. |
| Your key | Your browser calls the provider directly. | An Anthropic key or any OpenAI-compatible endpoint, including Ollama or LM Studio on your machine. |
The loop
- You ask. The composer takes text and, with the “+” button, a file, a selection, an image or the preview console.
- The model works. In Agent mode it reads files, writes files and — under Balanced — runs the checks it can. Every write asks for consent first.
- The checks run. A written page is parsed for errors, checked for a script that promises behaviour the markup cannot deliver, and, when nothing else is broken, loaded in Preview and read back for thrown errors.
- You review. Changes shows each edit; keep it, undo it, or revert the whole run. Then commit and push when you are happy.
What “checked” means
The receipt at the end of a run separates two things: parsed clean, not run when nothing exercised the output, and checked by running it when the page was loaded and read back with no errors. The checks can tell you a page is broken; they do not make a small model write a working one. A bigger model or your own key closes that gap.
On your device, not ours
Your code, your prompts and the model itself stay on your device. OIOXO’s servers see token counters for the free allowance, a few usage-stage beacons you can turn off, and — only if you send one — a problem report. Git push, pull and clone travel through a proxy on oioxo.com because browsers cannot speak Git’s protocol directly. The full list is the Privacy promise.