Zero Commit wishlist is opening soon — free to test, first 200 users get lifetime access. Try for free
01 How it works

A protocol, a paste,
and a reviewable PR.

Zero Commit isn't a smarter model and it isn't an autonomous agent. It's the layer that turns any LLM's answer into applied, reviewable changes in your repository.

02 Why a protocol

Most tools force you to change. This one doesn't.

Most AI coding tools try to force you into their model, their editor, or their agent. We did the opposite. The Zero Commit protocol is a short set of instructions you paste into whatever LLM you're already using. It tells the model to answer like a machine needs to read it.

01

Edits only, strict format

Search/replace blocks, full files, console commands. No preamble, no explanation, no recap. Everything the model writes is something Zero Commit can apply.

02

Search/replace over rewrites

The protocol understands the cost trade-off, so your output tokens aren't wasted re-sending unchanged code.

03

A footer you can trust

Every response ends with a list of changed files and a total count — a summary Zero Commit can cross-check before anything stages.

04

No guessing

If the model needs a file it wasn't given, it says so. It doesn't invent the content. Missing context surfaces instead of silently corrupting your code.

05

Console commands, first-class

Moves, renames, deletes, undos, pushes, PRs — the protocol can emit them, and Zero Commit executes them in order.

06

Model-agnostic by design

Any model that follows instructions can drive Zero Commit. You keep the model. You keep the chat subscription. You drop the copy-paste.

Input

Repository ingestion

Small repo? Turn it into one readable .txt file — structure plus source, ready to paste into any LLM.

Input

Deep Map

Big repo? Deep Map gives the model a structured view of the codebase so it can identify the files that matter for the task. You don't blow your context window shipping everything.

03 The core

Detect and Stage.

Paste the LLM's answer. Click Detect and Stage. Zero Commit reads the response, identifies each file operation, and stages the changes against your project.

01

Supported operations

File edits, new files, moves, renames, deletions, plus console directives the protocol can emit — :undo, :push, :pr, :doctor, and more.

02

Staged, not shipped

Staged changes aren't shipped changes. They're changes you review. Nothing lands until a human says yes.

03

Dozens of files, seconds

Multi-file changes stage together. No Ctrl+F, no search/replace by hand, no file-by-file grind.

04 Iteration

Turns — iterate without committing.

AI rarely nails it on the first try. Turns lets you stack follow-up LLM responses — Turn 2, Turn 3, however many it takes — on top of the same working state. Each turn builds on the last. You don't commit the junk in between.

When it's right, you ship. When it wasn't, you didn't create history you have to clean up.

05 Review, then ship

AI changes stay off your main branch until a human says yes.

Connected to a local Git repo, Zero Commit gives you a file view, a patch editor, and a Review & Ship action. From there, changes can move to GitHub on a dedicated branch — for example, feature/ai-patch — as a pull request for review.

06 Everything else

One tab, until it's done.

Built-in terminal and activity log. Deployment status for GitHub Actions and Cloudflare Workers/Pages. ZIP import that pushes a project into a GitHub repo in a few clicks. The point: fewer tabs, fewer dashboards, fewer context switches.

Stop applying AI changes by hand.

Join the wishlist. Testing is free. First 200 users get lifetime access at launch.