entireio/cli

📜 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.

Entire CLI – AI‑augmented Git workflow

What it is – Entire is a command‑line tool that hooks into your Git repository and records every interaction you have with an AI coding assistant (Claude, Codex, Cursor, etc.). Each AI session is stored as a checkpoint in a special Git ref, linked to the commit that created it. The result is a searchable, versioned transcript of why code changed, not just what changed.


Quick install

Platform Method
macOS / Linux brew install --cask entireio/tap/entire
Windows PowerShell: `irm https://entire.com/install.ps1
Any OS (Go) go install github.com/entireio/cli/cmd/entire@latest

You can also fetch a specific version or use the nightly channel via the same scripts.


Core concepts

Concept Meaning
Session One complete AI interaction (all prompts, responses, files touched).
Checkpoint A snapshot saved when you make a Git commit. Stored as a Git ref refs/entire/checkpoints/<shard>/<id> and linked to the commit via an Entire-Checkpoint trailer.
Checkpoint storage Metadata lives in Git objects (not in branch history), so your code history stays clean while the AI context is versioned and fetchable on demand.
Agent hooks Entire installs Git hooks that capture the AI‑agent traffic; you can add or remove agents with entire agent.

Typical workflow

  1. Enable in a repo: entire enable (adds hooks, creates .entire/settings.json).
  2. Work with your usual AI assistant; Entire runs silently in the background.
  3. Commit as normal – the hook adds an Entire-Checkpoint trailer and writes a checkpoint ref.
  4. Resume a past session: entire session resume <branch> restores the checkpoint metadata so you can continue where you left off.
  5. Search / audit: entire search, entire checkpoint explain, or entire recap to view transcripts, token usage, files changed, etc.

Main commands (high‑level)

  • entire enable / disable – turn Entire on or off for the current repo.
  • entire status – show whether Entire is active and current session info.
  • entire agent – add/remove/list supported AI agents.
  • entire session … – list, inspect, stop, attach, or resume AI sessions.
  • entire checkpoint … – list, explain, or search stored checkpoints.
  • entire search – semantic/keyword search across checkpoints and commits.
  • entire login / logout – authenticate with the Entire control‑plane (browser flow or device‑code flow for headless CI).
  • entire doctor – diagnostics and cleanup utilities.

Why use Entire?

  • Traceability – Every prompt, response, file edit, token count, and tool call is archived alongside the commit that introduced the change. Helpful for audits, compliance, or onboarding new team members.
  • Clean Git history – No extra commits are added to your branch; AI context lives in separate refs.
  • Resume work – Jump back into a paused AI session from any checkpoint, even on a different machine.
  • Searchable knowledge base – Use entire search to find past AI suggestions, making the repo a living documentation source.
  • Works with any Git workflow – Supports worktrees, multiple concurrent sessions, and co‑exists with existing Git hooks.

Security & privacy notes

  • Tokens are stored in the OS keyring by default; headless environments can use a file‑backed store (ENTIRE_TOKEN_STORE=file).
  • For CI, supply a token via ENTIRE_TOKEN to avoid persisting credentials.
  • Checkpoint data is stored in Git refs, so it can be pushed, fetched, or stripped like any other Git object.

License

The repository is released under the terms specified in the LICENSE file (not reproduced here).


Bottom line – Entire turns AI‑assisted coding into a first‑class part of your version‑control workflow, giving you a permanent, searchable record of why code changed while keeping your Git history tidy.

Related

  • Project
  • Project
  • Project
  • Dispatch
  • Dispatch