Skip to content
OIOXO
The editor

Review & undo

Letting an AI edit a project you care about comes down to one question: what happens when it gets something wrong? OIOXO’s answer has three parts — you see every change before it lands, you choose which parts of it to keep, and anything that did land can be taken back.

See it before it lands

When the agent finishes a change it opens a review, not a commit. Each file is shown as a side-by-side diff, and each file has a checkbox. Uncheck one and it is left exactly as it was; a file the agent created is deleted again.

Keep some of it, not all of it

Within a file you can go finer. Every changed block — a hunk — has its own control, so if the agent made three edits to a file and you want two of them, you keep two. The button tells you what you are about to apply, including how many hunks you dropped. Nothing is all-or-nothing.

Tip

If a file changed underneath the review — you edited it, or another process did — OIOXO refuses to apply rather than merging blind. You get a clear failure instead of a quietly mangled file.

Undo it after the fact

Three separate safety nets run at once, and they survive closing the tab:

  • Every save is kept. The last 50 versions of each file, up to ~48 MB and 30 days. Identical saves cost almost nothing, so this is cheap to leave on.
  • Unsaved edits survive a reload. Close the tab mid-thought and the buffer is still there.
  • Each agent run snapshots the whole project. Step back to any point in a run — up to ~200 MB of history — not just the last change.

And a real Git repo, on your disk

Not a copy and not a sandbox: a genuine .git directory in your folder, even when you are working in a browser tab. Branch, stage, commit, diff and read the log as usual — then clone the folder on another machine and the history is intact, because it was never ours to begin with. Staging works hunk by hunk too.

Local operations need nothing but the folder. Pushing and pulling to a remote goes through your own machine when the local engine is connected, so your credentials stay where they already are.

What the agent is not allowed to do

  • Read your secrets — .env files, keys and credentials are off limits unless you turn that off for a project.
  • Run something destructive without asking, whatever your other settings say.
  • Write anywhere you marked off limits — you can set per-path rules in Settings.
  • Edit a project you imported from someone else: those open read-only until you say otherwise.