Entire CLI: Git Hooks That Capture AI Agent Sessions Alongside Commits
📜 Entire CLI hooks into your Git workflow to capture AI agent sessions as you work. Sessions are indexed alongside commits, creating a searchable record of how code was written in your repo.
At a glance
- What is it?
- Entire is a Go CLI that installs Git hooks to record AI agent sessions and index them next to your commits. It targets teams that need a searchable trail from prompt to change, and it stores that context outside branch history.
- Who is it for?
- Adopt Entire if your team already runs Claude Code, Codex, Gemini or Pi inside a Git repo and you need a searchable record of which prompts produced which commits, especially where audit or handover matters. Do not adopt it if you work mostly outside Git, or if you cannot accept that session transcripts and token usage are captured by hooks and may be pushed to a checkpoint remote.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly Go, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
The gap Entire fills: commits without their prompts
Git records what changed. It does not record why an agent was asked to change it. The Entire README frames the product around that gap: sessions are indexed alongside commits, so the prompt and response transcript, the files touched, token usage and tool calls sit next to the commit they produced. The stated audience is developers and teams who use coding agents inside a repository and later need to answer why a line changed. The README lists onboarding and audit or compliance traceability as the intended outcomes. That is a narrower pitch than general observability for AI tools. Entire does not try to score model output or manage prompts. It attaches a session record to a Git repository and makes that record searchable. If your agents run outside a Git working tree, the premise does not apply to you.
Sessions, checkpoints and where the data lives
The README defines two core concepts. A session is a captured agent interaction. A checkpoint is a point in a session you can return to. The design decision that matters most is storage: the README states that agent context lives outside your branch's history, which is what lets the project claim it keeps Git history clean. Practically, that means the session record is not a commit on your branch, and the branch you push to your team does not carry the transcripts. The README also describes a checkpoint remote as a configurable setting, updated through entire configure. So the material supports this reading: captured sessions are indexed against commits, and checkpoint data can be sent to a remote that you choose. What the README excerpt does not spell out is the exact on-disk layout or the wire format of a checkpoint. If you need to know precisely which files land on disk before you enable this in a regulated repository, that detail is not in the supplied material and you would have to read the source or the full docs.
Installing on macOS, Linux and Windows
The README gives several install paths. On macOS and Linux, Homebrew is the packaged route: brew tap entireio/tap, brew trust entireio/tap, then brew install --cask entire. A nightly cask exists as entire@nightly. The install script is curl -fsSL https://entire.io/install.sh | bash, with a --channel nightly flag for prereleases. On Windows, irm https://entire.io/install.ps1 | iex handles stable, and the script uses Scoop when available, otherwise it verifies the release checksum and installs entire.exe and git-remote-entire.exe into %USERPROFILE%\.local\bin. Scoop users can run scoop bucket add entire https://github.com/entireio/scoop-bucket.git followed by scoop install entire/entire. There is a Go route for development: go install github.com/entireio/cli/cmd/entire@latest, plus a second binary, git-remote-entire, which resolves entire:// URLs for entire repo clone and git clone entire://. The README notes that a go install build leaves experimental commands visible in entire help, unlike a stable packaged install. The README also documents a Scoop package rename from cli to entire, with a migration command that installs the new package before removing the old one.
Enabling a repository and the commands you actually type
Setup is two steps in the README's Quick Start. Run cd your-project && entire enable, then entire status to check state. On a repository that has not been enabled before, enable runs an initial flow: it creates Entire settings, installs Git hooks, and prompts for which agent hooks to install. For scripted setup, entire enable --agent <name> skips the prompt; the README's example is entire enable --agent cursor. Day-to-day, the README points to entire agent for adding or removing agents, entire configure for non-agent settings (it names telemetry, hooks, checkpoint remote and summary provider), and entire enable or entire disable to toggle the tool for a repository. The README also mentions a headless and CI authentication section and a plugins section, but the supplied excerpt does not include their contents, so the exact CI token flow cannot be described here. What is verifiable is the shape of the workflow: hooks capture while you work, and the CLI manages which agents are wired in.
Failure modes and the wrong-tool case
Two constraints stand out. First, the hooks are the capture mechanism, so anything that bypasses them is invisible. The README lists Git as a requirement and describes enabling per repository. An agent session run outside an enabled repository, or in a checkout where the hooks were not installed, produces no record. Second, the release cadence is unusual: the three most recent releases in the supplied data are all nightly builds with date-stamped tags, published daily. The README itself separates stable from nightly and recommends stable for most users, which tells you the nightly channel is where less-proven changes land. If you pin to nightlies for newer agent support, you accept that. There is also a Windows-specific trap documented in the migration notes: a live entire.exe locks its own shim, so the Scoop migration command must run when entire is not running. That is a concrete operational detail, not a hypothetical. Finally, the tool is the wrong fit if your compliance process forbids sending session transcripts to any remote at all, because the checkpoint remote is a first-class configuration option.
How it differs from plain Git plus agent logs
The obvious alternative is what most teams do today: let each agent write its own session files to a local directory, and rely on Git for the code. That approach has no shared index. Session files are not tied to commit SHAs, they are not searchable across the repository, and a coworker cannot resume from your checkpoint. Entire's difference is the indexing step: the README states sessions are indexed alongside commits, and that a versioned record of every AI interaction is tied to Git history. The second alternative is treating agent context as commits on the branch, which several tools do by committing transcript files. Entire explicitly rejects that, keeping agent context outside branch history. The trade-off is real in both directions. Keeping transcripts off the branch means your diffs stay readable, but it also means the record lives in a separate store you must back up and access deliberately. Committing transcripts makes them travel with clones automatically, at the cost of noisy history. Entire picks the first option and adds a checkpoint remote to cover the sharing case.
Licence, maintenance and upgrade cost
The repository is MIT licensed, which permits commercial use and modification with the usual requirement to retain the copyright and permission notice. That is the standard permissive position; it is not legal advice, and if you redistribute a modified build you should read the licence text yourself. On maintenance, the supplied data shows a push within the last day of the snapshot and a daily nightly tag stream, which indicates active development rather than a dormant repository. The upgrade cost is mostly channel management. Stable users upgrade through Homebrew, Scoop or the install script and get fewer, larger changes. Nightly users get daily builds and should expect less-proven behavior. If you install via go install, remember the README's note that experimental commands stay visible in entire help, so your help output will not match a packaged stable install. The Scoop rename from cli to entire is a one-time migration cost for Windows users who installed the old package name.
Editorial conclusion
Adopt Entire if your team already runs Claude Code, Codex, Gemini or Pi inside a Git repo and you need a searchable record of which prompts produced which commits, especially where audit or handover matters. Do not adopt it if you work mostly outside Git, or if you cannot accept that session transcripts and token usage are captured by hooks and may be pushed to a checkpoint remote. Before rolling it out, run entire status after entire enable on a throwaway branch, then push to your real remote and confirm what the checkpoint remote actually receives, since that is the boundary that decides whether this tool fits your compliance posture.
Community notes