Entire CLI
Agent session history is linked to Git commits so a change can be traced to its original prompt, conversation and affected files.
- 5,310 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Hooks retain prompts, conversation and session files, which are pushed to the Git remote by default.
- Entire login and its GitHub App add operations over accessible projects and repository mirrors.
Install
- Works in
Manual install
brew install --cask entireio/tap/entire # macOS and LinuxFirst Install method for macOS and Linux; Git is required.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Hooks retain prompts, conversation and session files, which are pushed to the Git remote by default.
- Entire login and its GitHub App add operations over accessible projects and repository mirrors.
This is third-party code. Review the repository files before installing.
What it does
Enabling Entire in a repository installs Git hooks and hooks for selected agents. A commit containing agent work receives a link to a checkpoint containing prompts, conversation and touched files. Search can retrieve checkpoints alongside commits and sessions. The CLI also manages Entire-hosted repositories and GitHub mirrors. It can open a Trail, a change-review page where agents evaluate pushes and report findings. Local session capture needs no account; hosting and server features require signing in.
Who it is for. Teams using coding agents that need to recover the reasoning and conversation behind a commit.
Good fit when
- A review needs the prompt that led to a code change.
- Work should resume from retained conversation on another branch.
- You need to inspect checkpoints that will accompany a code push.
- After a CLI update, agent events are no longer captured and the team checks its installed hooks.
Not a fit when
- Project policy prohibits retaining agent conversations in Git storage.
- Checkpoints must stay private but the selected remote is public.
- The team does not permit changes to Git hooks or agent configuration.
Example request
Show Entire status and checkpoints queued for upload in this repository. Do not push code or conversations.Limitations
Checkpoints use separate Git refs and are pushed alongside code by default; anyone can read them in a public repository. Secret redaction is best effort, so inspect checkpoint content before pushing. GitHub mirrors require the Entire GitHub App on the selected repository. A custom server-side review agent requires project billing to be configured before it can run; local session capture works without an Entire account.
How to disable. Run `entire disable` to stop capture or `entire disable --uninstall` to remove Entire from the repository. Previously pushed checkpoints need separate deletion.
FAQ
How do I enable capture in an existing project?
Run `entire enable` in the Git repository, choose agents, then run `entire status` to inspect sessions and checkpoint destinations.
How do I inspect the next upload?
Run `entire checkpoint list --outgoing`, then `entire checkpoint explain <id>` for each selected checkpoint before pushing.
How do I keep sessions local?
Run `entire configure --local --skip-push-sessions`, then check the destination in `entire status`. Local capture and server uploads are separate settings.
How do I find earlier work context?
Use `entire search` across sessions, commits and checkpoints, then inspect a hit with `entire checkpoint explain <id>`.
How do I restore agent hooks after a CLI update?
Run `entire agent add <name>` with the connected agent’s name. If capture still fails, use `entire doctor` for diagnostic information.
Discussion
No questions or reviews yet.
Related
CLI toolsA CLI for instant search across coding-agent session history on your machine, like git blame for sessions
A tmux-based TUI that runs Claude Code, Codex and other agents in one list: status, quick prompts, worktrees and diff review
A CLI and skill that gather coding-agent session history into one SQLite file the agent can search for past decisions
Decision memory in git: AI agent sessions are saved at commit time, and an agent can recall the reasons and rejected options
dmux is a terminal agent manager for tasks across repositories in one session, keeping hidden panes running in the background.
A CLI for AI agents sharing a repository: a task board, a spec and acceptance by a second agent against a specific commit
README in short
The client preserves existing Git hooks and adds an `Entire-Checkpoint` trailer. Session storage does not add separate commits to the working branch.