Entire CLI: Version Control for Your Agent Sessions

When you use AI coding agents like Claude Code, the code stays but the conversation disappears. You get the commit, but not why the agent made the choices it did. Entire fixes that.

It hooks into your git workflow to capture AI sessions — prompts, responses, files touched, token usage — and stores them on a separate git branch (entire/checkpoints/v1). Your commit history stays clean. The context lives alongside it.

30s Setup

# Install
curl -fsSL https://entire.io/install.sh | bash

# Enable in any git repo
cd your-project
entire enable

Running entire enable in the magerblog repo — hooks installed, checkpoint branch created, ready to go

That's it. Work with Claude Code or Gemini CLI normally. When you push, Entire prompts you to link the commit to your session. If you say yes, the session gets pushed to your repo as a checkpoint.

Strategies

Entire has two strategies: manual-commit (default) and auto-commit. I'd recommend auto-commit — it creates a checkpoint after every agent response, so you get fine-grained save points without having to remember to commit yourself:

entire enable --strategy auto-commit

Rewind

The standout feature. Entire saves checkpoints as you go. If things go sideways, roll back:

entire rewind

Pick a checkpoint, code snaps back. No git stash, no manual undo. You can also use entire explain to review what happened in a session or entire resume to pick up where you left off.

Real Example

I used Claude Code to refactor the navigation on this blog — making the header consistent across all pages. Entire captured the full session automatically.

Running entire explain shows each checkpoint with the original prompt and resulting commit. And entire rewind gives you an interactive picker to roll back to any save point:

entire explain showing session checkpoints, and entire rewind with an interactive selector to roll back

Works Across Machines

The config files (.entire/settings.json, .claude/settings.json) get committed to your repo. On a new machine, just install the CLI and re-enable hooks:

curl -fsSL https://entire.io/install.sh | bash
git pull origin main
entire enable --force

Sessions from all your machines push to the same checkpoint branch.

What It Doesn't Touch

Entire is local dev tooling. No build changes, no CI/CD impact, no new dependencies. Your deploys stay exactly the same.

One More Thing

Honestly, this feels like something that should just be built into Claude Code. Running a separate CLI for session history adds friction. But the tradeoff makes sense — Entire is agent-agnostic (works with Gemini CLI too) and stores everything in git, not a vendor's cloud. If Anthropic built it in natively, it'd only cover Claude. Having it as a git layer means the history lives in your repo regardless of which agent wrote the code.

Overall it was a good experience getting it set up across my projects. I'm excited to see how it evolves.

Check it out: entire.io · GitHub · Docs