A Claude Code GUI from the first prompt to the merge

Oxide is a desktop GUI for the claude CLI you already have: the same login, the same sessions, with each Turn's changes and checks in view.

Oxide is a free, open-source desktop app for agentic coding that drives Claude Code, Codex and Antigravity CLI in one window and shows what each change touched and what was actually checked, so you can merge with confidence.

What Oxide adds to Claude Code

Every Turn gets its own diff, so you read what one prompt changed instead of scrolling a transcript. Oxide takes a Checkpoint when the Turn starts and another when it ends, which is what makes that diff exact.

The Verification Dossier shows which checks actually ran, which went stale and what no check covers: see what the Dossier shows. Line comments go back to Claude Code as one prompt.

What stays the same

Claude Code still does the work, with your login and your plan. Each Thread maps one-to-one to a Claude Code session, and its Slash commands and skills are in the composer.

Oxide drives the CLI rather than replacing it: install Claude Code once, and it shows up as a Provider.

Undo a Turn, not just a file

Restore puts the files back to how they were before any Turn, and the Restore itself can be undone. Claude Code is told on its next prompt which files went back.

To take out one file or one hunk instead, use Revert: Revert and Restore covers both.

Let another Provider review it

Have Codex or Antigravity CLI review Claude Code's change in a Blind review, seeing only the diff and the issue. Its findings become Line comments you keep or dismiss.

How a Blind review works, and the full setup in Claude Code and Codex together.

GUI or terminal?

The terminal is still the fastest way to fire off a prompt. A GUI pays off at review time: per-Turn diffs, the Dossier, comments on lines and the pull request in one window.

How to review AI-generated code is the method behind it, with or without Oxide.

Questions

Do I need Claude Code installed first?

Yes. Oxide drives the claude CLI; it doesn't replace it. Install Claude Code and log in once in a terminal, then launch Oxide and it shows up as a Provider. Requirements.

Can I keep using my Slash commands and skills?

Yes. The composer lists Claude Code's own Slash commands and skills, because the Thread is a real Claude Code session, not an imitation of one.

How do permission modes map to Claude Code?

Each Thread runs in Ask, Auto-edit or Full access, and you can change the mode between Turns. When Claude Code asks for an Approval, you answer it inline; the Attention Center lists every Thread waiting on you.

Does Oxide work with Claude Code on Windows?

Yes. Oxide runs on macOS on Apple Silicon and Windows x64, and on Windows it drives the claude CLI installed there, with the same Diff, Dossier and Restore as on macOS.

What happens to my Claude Code sessions?

Each Thread maps one-to-one to a Claude Code session. Deleting a Thread removes Oxide's own record of it (Transcript, Checkpoints, worktree) and leaves Claude Code's session files alone.

Take your next Turn all the way to the merge.

Oxide drives the Claude Code, Codex or Antigravity CLI you already use. Open a Project, start a Thread and review what comes back.