Git-native context for AI coding agents

Git for multi-agent coding.

One source of truth for your agents and your team. Entire records every agent session as a checkpoint linked to the commit it produced — so the why lives in your repo, not a closed terminal.

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

See how it works →

MIT licensed · Works with every coding agent · Hooks into your existing workflow

~/app — entire CLI

$entire enable ✓ hooks installed for claude-code, codex, gemini ✓ session capture: active $git commit -m "fix: TestHTTPServer race in parallel mode" [main a4f1c92] fix: TestHTTPServer race in parallel mode 1 file changed, 34 insertions(+), 8 deletions(-) → [entire] session 9b1deb4d linked to a4f1c92 $entire explain --commit a4f1c92 Agent: claude-code · Files: 1 · Tokens: 8.4k Summary: wrapped listener handoff in sync.Once + barrier Why sync.Once over mutex: listener created once, read many.

Works with every coding agent

01 — The problem

Git knows what changed. Entire knows why.

Without that why, sessions disappear when you close the terminal, parallel agents overwrite each other, and a bad run has no rewind. Developers spend more time reconstructing context than shipping. Entire captures every session as a checkpoint linked to the commit it produced.

Your agent's thinking dies with the terminal.

A 2-hour Claude run becomes scrollback you'll never reconstruct. entire explain brings the session back — prompts, files touched, the reasoning behind the diff — linked to the commit it produced.

demo

$ entire explain --commit a4f1c92

Commit a4f1c92 · Fix flaky test race

Agent: claude-code · Files: 1 · 8.4k tokens

Summary

The listener was shared across goroutines

without synchronization. Wrapped handoff

in sync.Once + added a goroutine barrier.

Parallel agents stomp on each other's work.

Run Claude and Codex in the same repo and you're one git checkout from blowing away a half-finished refactor. entire enable installs hooks for every agent. entire resume <branch> drops you back into the right session on the right branch.

demo

$ entire status

2 active sessions · 2 worktrees

● claude-code · refactor-auth

~/app/wt/refactor-auth

● codex · review-pr-1247

~/app/wt/review-pr-1247

There's no undo button for a bad agent run.

One confidently-wrong patch poisons the next ten prompts. entire rewind jumps you back to any prior checkpoint so you can branch from a known-good state.

demo

$ entire rewind --list

↺ Rewind points

● a4f1c92 · 2h ago · Fix flaky test

● b81e2a0 · 3h ago · Expired-token fix

● c91f3d4 · 4h ago · Initial refactor

→ entire rewind --to b81e2a0

02 — The team payoff

Software is a team sport. When agents join, misalignment costs more.

The pull request was never built for this. It used to align humans on code humans wrote. Now it's where teams try to align on code an agent wrote, from a session no one saw. The diff lands, the reasoning doesn't. Entire makes the session travel with the commit. The author, the reviewer, the next agent all read from the same trail.

Agent Claude Code 2:00pm

Wrote the code "SessionCache is referenced in five spots, all read-only. Safe to swap for TokenStore."

~/app/wt/refactor-auth > Refactor auth middleware to use the new TokenStore. Read internal/auth/middleware.go Grep -r "SessionCache" internal/ Edit middleware.go (+62 -41) Edit token_store.go (+18 new) Tests · 89 passed

commit c3a91f4 checkpoint linked

Agent Codex 2:40pm

Reviewed with full context "This misses the expired-token case the earlier session already fixed."

~/app/wt/refactor-auth-review $ entire explain --commit c3a91f4 | codex review Reading Claude's session 9b1deb4d. Note: TokenStore.Get misses the expired-token case the earlier session at b81e2a0 already fixed.

refs b81e2a0 checkpoint linked

Human dipree 3:15pm

Opens the commit on entire.io "Why TokenStore?" "Did anyone check the expired-token path?" Both answered.

●entire.io/entireio/cli/commits/c3a91f4

refactor: auth middleware uses TokenStore

Diff Sessions (2)

Claude

2:00pm · 1h 12m SessionCache → TokenStore swap, five spots, read-only paths only.

Codex

2:40pm · refs b81e2a0 Flags missing expired-token case from prior fix.

commit c3a91f4 2 sessions

03 — How it works

Every agent picks up where the last one left off.

Session context lives in your repo, so no agent — and no developer — ever starts from scratch. Run Claude in the morning, hand off to Codex in the afternoon, kick off a migration to Gemini next week. Every one of them starts with the full history of what the others did.

01 · CAPTURE EVERY AGENT

One hook, every agent.

One entire enable installs hooks for every agent you use — Claude Code, Codex, Gemini, Cursor, Copilot CLI, Factory, OpenCode. Whichever agent writes the code, the session lands in the same repo.

CLI terminal

my-repository % entire enable

? Which agents are you using?

Use space to select, enter to confirm.

[✓]Claude Code

[ ]Codex

[ ]Gemini CLI

[ ]Cursor

[ ]OpenCode

[✓]Copilot CLI

✓ 2 agents enabled

✓ session capture: active

entire.io / entireio/cli / overview

0cacc35 feat(review): failures and live multi-agent progress… Codex Claude +1311/-25

c0138f7 review: refine empty-manifest explainer and clean up… Claude +111/-6

718f92e fix(review): address PR bot feedback Claude +30/-25

3a7f334 test(review): cover streaming, missing-terminal paths Claude +178/-2

87aab26 review: address PR feedback on enricher plumbing Claude +208/-22

a3d29fe feat(review): stream codex via exec --json Claude +96/-876

56bc6e7 feat(review): default scope to mainline, add --base… Claude Codex +762/-301

02 · LINK TO COMMITS

Code and context, together.

Each session is condensed into a checkpoint linked to the commit it produced — the commit points back, the session points forward.

CLI on commit / push

$ git commit -m "fix: TestHTTPServer race"

[main a4f1c92] fix: TestHTTPServer race in parallel mode

1 file changed, 34 insertions(+), 8 deletions(-)

[entire] capturing session 9b1deb4d…

✓ checkpoint 7f3a2b1 linked to a4f1c92

✓ trailer added: Entire-Checkpoint: 7f3a2b1

$ git push origin main

[entire] pushing 1 checkpoint to entire/checkpoints/v1

✓ done · view on entire.io →

entire.io / sessions / 9b1deb4d

C

Claude Code

279 steps

Briefing: Per-agent live streaming for entire review. Background — PR #1184 fixed the drill-in viewport for entire review multi-agent runs. One issue explicitly deferred from that PR…

Background

PR #1184 (just merged) fixed the drill-in viewport for multi-agent runs.

Current behavior (the problem)

RunMulti fans events from per-agent goroutines into a single dispatch loop

The TUI sink is ready to display events as they arrive

The bottleneck is upstream — each agent's reviewer/parser doesn't emit AssistantText…

Filters

✓

Prompts 36

✓

Responses 239

✓

Steps 203

✓

Checkpoints 1

Tool calls 221

✓

File edits 57

✓

Bash 87

✓

03 · ANY AGENT RECALLS ANY SESSION

Hand off context, not explanations.

Hand any agent a session ID or commit SHA and it pulls the full prior context — regardless of which agent originally produced it. Tell Codex to review Claude's session from yesterday.

CLI entire explain

$ entire explain --commit a4f1c92

Commit a4f1c92 · Fix flaky TestHTTPServer race

Agent: claude-code · Session: 9b1deb4d

Files: 1 · Tokens: 8.4k

Summary

The listener was shared across goroutines

without sync. Wrapped handoff in sync.Once

+ added a goroutine barrier.

Why sync.Once over a mutex?

Listener is created once, read many times.

Mutex would serialize every test read.

$ entire explain --commit a4f1c92 | codex review

entire.io / dispatches / entireio-cli

Repos

entireio/cli

Branches

main

Window

6 May → 13 May

Dispatch for entireio/cli

voice: Marvin · generated from 47 checkpoints

Another week where the code seemed determined to surprise us with previously unknown failure modes, as if we hadn't already catalogued enough ways for things to go sideways.

The Great Performance Optimization Campaign

The checkpoint migration command decided to take extended coffee breaks, clocking in at 20-30 minutes for 4k checkpoints. Investigation revealed 99% of time was spent in unnecessary archive metadata repairs. Batch writes reduced ref updates from ~2478 to ~25 operations…

Review Command Archaeology

Multiple regressions surfaced in the recently refactored review command, each more creative than the last. The environment variable handshake between parent and child processes had silently broken, causing review sessions to lose their tagging…

04 · ANY AGENT PICKS UP WHERE ANY OTHER LEFT OFF

Rewind. Resume. Branch.

Rewind to any checkpoint and branch from a known-good state, regardless of which agent created it. Resume the original session on the right branch, or hand off to a different agent at the same checkpoint.

CLI entire rewind · resume

$ entire rewind --list

↺ Rewind points (current session)

● a4f1c92 · 2h ago · Fix flaky test (current)

│

● b81e2a0 · 3h ago · Expired-token fix

│

● c91f3d4 · 4h ago · Initial refactor

$ entire rewind --to b81e2a0

✓ rewound to b81e2a0

$ entire resume refactor-auth

✓ resumed session 9b1deb4d on refactor-auth

entire.io / checkpoints / 7f3a2b1

a4f1c92 ⇄ checkpoint 7f3a2b1 linked

Commitfix: TestHTTPServer race in parallel mode

Agentclaude-code

Session9b1deb4d

Duration1h 12m · 8.4k tokens

Branchmain

internal/server/http_test.go +34 -8

04 — Privacy

Privacy, baked in by design.

→

Secrets stay secret.

Entropy + 260+ known patterns.

→

Redacted in-process.

Nothing leaves your machine raw.

→

Credentialed URIs caught.

JDBC, DSNs, tokens, secret pairs.

→

PII stays redacted.

Emails, phones, addresses, custom patterns.

→

Redacted before commit.

Sanitized at storage boundaries.

→

Remote checkpoints.

Push session history to a separate private repo. Public codebase, private context.

Start capturing your intent.

Entire is open source. Yours to fork, run, and extend. Install it once, and never lose the context behind your commits again.

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

★ Star on GitHub Read the docs →

⚡ Join the rebellion

It's time for a new developer lifecycle. We're rebuilding it.

Monthly updates from the front lines. Developer news, curated content, early access, and exclusive drops for people who got here first.

What you'll get

✉

Monthly newsletter

Front-line dispatches from the team rebuilding the developer lifecycle.

↗

Early access

First look at features before they ship to the broader CLI and entire.io.

★

Exclusive drops

Curated content, technical deep-dives, and goods reserved for the early crew.

— Sign up

Get on the list.

No spam. One email a month. Unsubscribe anytime.

✓ You're in

Thanks for joining the rebellion.

Join our Discord to stay up to date and look out for all the goodness hitting your inbox.

Join our Discord ← Back to home

Check your inbox for a confirmation. The first dispatch lands in your inbox at the start of next month.