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 the same CLI also covers Entire's Git hosting and Trails review.
- Who is it for?
- Adopt Entire if your team already runs Claude Code, Codex, Cursor, Copilot CLI, OpenCode 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 agent sessions are captured by hooks as checkpoints and uploaded to a destination that entire status reports.
- 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 November 15, 2026, and from our analysis. They are not legal advice.
Star history
- entireio/cli5,337 ★ · +246
| Repository | 2026-09-13 | 2026-11-15 |
|---|---|---|
| entireio/cli | 5.1k | 5.3k |
246 Stars in the last 63 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial 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. Entire's repository description frames the CLI around that gap: it hooks into your Git workflow to capture AI agent sessions as you work, and sessions are indexed alongside commits, creating a searchable record of how code was written in your repo. The README now presents Entire more broadly, as a Git forge built for agent-human collaboration: besides session capture (continuous memory, where every agent session is captured as a checkpoint linked to your commits), the CLI covers distributed Git hosting on Entire's Git-compatible server or GitHub mirrors, and Trails, which give a heads-up display for each change with customizable evals that agents score on every push. Session capture works in any Git repository with no account needed; 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's Agent Sessions pitch is continuous memory: every agent session is captured as a checkpoint linked to your commits, and entire-brain combines those checkpoints with entire-graph's code map into project memory. After entire enable, entire status shows current sessions and where checkpoints are uploaded. The README's contents also list a Security & Privacy section; read it and the docs at docs.entire.com before enabling capture in a regulated repository.
Installing on macOS, Linux and Windows
The README gives three stable install commands: brew install --cask entireio/tap/entire on macOS and Linux, curl -fsSL https://entire.com/install.sh | bash on macOS and Linux without Homebrew, and irm https://entire.com/install.ps1 | iex in Windows PowerShell 5.1+. The nightly channel, described as prerelease builds with the latest changes, uses brew install --cask entireio/tap/entire@nightly, curl -fsSL https://entire.com/install.sh | bash -s -- --channel nightly, or iex "& {$(irm https://entire.com/install.ps1)} -Channel nightly". Git is required on macOS, Linux or Windows. Scoop, go install and installing during a GitHub outage are covered in the Installation docs at docs.entire.com rather than in the README. Clones use entire:// URLs through the git-remote-entire helper that ships with the packaged installs.
Enabling a repository and the commands you actually type
Session capture is the first step of the README's Quick Start: cd your-project, then entire enable, which lets you pick your agents and installs their hooks along with Entire's git hooks, then entire status to see current sessions and where checkpoints are uploaded. It works in any Git repository and needs no account. To put a repository on Entire itself, you run entire login, then either entire repo mirror add to mirror a GitHub repository into one or more clusters (which needs the Entire GitHub App installed for that repository) or entire project create and entire repo create for an Entire-native one, clone it with entire repo clone, and run entire enable inside the clone. The third step opens a Trail on your working branch with entire trail create and entire trail show. 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 are all nightly builds with date-stamped tags, published within days of each other. The README separates stable from nightly and describes nightly as prerelease builds with the latest changes. If you pin to nightlies for newer agent support, you accept that. Finally, entire status reports where checkpoints are uploaded, so confirm that destination fits your compliance process before enabling capture.
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 the README describes each agent session as a checkpoint linked to your commits, with entire status showing where checkpoints are uploaded.
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 repository shows a recent push and a daily nightly tag stream, which indicates active development rather than a dormant repository. The upgrade cost is mostly channel management. Stable users install through Homebrew or the install scripts. Nightly users get prerelease builds with the latest changes.
Editorial conclusion
Adopt Entire if your team already runs Claude Code, Codex, Cursor, Copilot CLI, OpenCode 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 agent sessions are captured by hooks as checkpoints and uploaded to a destination that entire status reports. Before rolling it out, run entire status after entire enable on a throwaway branch, then push to your real remote and confirm where checkpoints are uploaded, since that is the boundary that decides whether this tool fits your compliance posture.
Frequently asked questions
How do I install Entire CLI on macOS or Linux?
Run `brew install --cask entireio/tap/entire`. Without Homebrew, run `curl -fsSL https://entire.com/install.sh | bash`, with `--channel nightly` passed after `bash -s --` for the prerelease line.
Where are Scoop and go install installs documented?
The README's install section covers the Homebrew, install-script and PowerShell routes and sends Scoop, `go install` and installing during a GitHub outage to the Installation docs at docs.entire.com.
Can I install a nightly build of Entire CLI with Scoop?
Scoop installs are covered in the Installation docs at docs.entire.com rather than in the README. On Windows the README's nightly route is the PowerShell installer: `iex "& {$(irm https://entire.com/install.ps1)} -Channel nightly"`.
What does entire enable do in a repository?
It lets you pick your agents and installs their hooks along with Entire's git hooks; it works in any Git repository and needs no account. Use `entire status` to see current sessions and where checkpoints are uploaded.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/entireio-cli)Star history chart for your README
[](https://hysenlabs.com/projects/entireio-cli)Was this useful?