内容摘录
Entire CLI
Entire 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.
With Entire, you can:
**Understand why code changed** — see the full prompt/response transcript and files touched
**Recover instantly** — rewind to a known-good checkpoint when an agent goes sideways and resume seamlessly
**Keep Git history clean** — preserve agent context on a separate branch
**Onboard faster** — show the path from prompt → change → commit
**Maintain traceability** — support audit and compliance requirements when needed
Table of Contents
Quick Start
Typical Workflow
Key Concepts
How It Works
Strategy
Commands Reference
Configuration
Security & Privacy
Troubleshooting
Development
Getting Help
License
Requirements
Git
macOS or Linux (Windows via WSL)
Claude Code, Gemini CLI, or OpenCode installed and authenticated
Quick Start
Typical Workflow
Enable Entire in Your Repository
This installs agent and git hooks to work with your AI agent (Claude Code, Gemini CLI or OpenCode). You'll be prompted to select which agents to enable. To enable a specific agent non-interactively, use entire enable --agent <name> (e.g., entire enable --agent opencode).
The hooks capture session data as you work. Checkpoints are created when you or the agent make a git commit. Your code commits stay clean, Entire never creates commits on your active branch. All session metadata is stored on a separate entire/checkpoints/v1 branch.
Work with Your AI Agent
Just use Claude Code, Gemini CLI, or OpenCode normally. Entire runs in the background, tracking your session:
Rewind to a Previous Checkpoint
If you want to undo some changes and go back to an earlier checkpoint:
This shows all available checkpoints in the current session. Select one to restore your code to that exact state.
Resume a Previous Session
To restore the latest checkpointed session metadata for a branch:
Entire checks out the branch, restores the latest checkpointed session metadata (one or more sessions), and prints command(s) to continue.
Disable Entire (Optional)
Removes the git hooks. Your code and commit history remain untouched.
Key Concepts
Sessions
A **session** represents a complete interaction with your AI agent, from start to finish. Each session captures all prompts, responses, files modified, and timestamps.
**Session ID format:** YYYY-MM-DD-<UUID> (e.g., 2026-01-08-abc123de-f456-7890-abcd-ef1234567890)
Sessions are stored separately from your code commits on the entire/checkpoints/v1 branch.
Checkpoints
A **checkpoint** is a snapshot within a session that you can rewind to—a "save point" in your work.
Checkpoints are created when you or the agent make a git commit. **Checkpoint IDs** are 12-character hex strings (e.g., a3b2c4d5e6f7).
How It Works
Checkpoints are saved as you work. When you commit, session metadata is permanently stored on the entire/checkpoints/v1 branch and linked to your commit.
Strategy
Entire uses a manual-commit strategy that keeps your git history clean:
**No commits on your branch** — Entire never creates commits on the active branch
**Safe on any branch** — works on main, master, and feature branches alike
**Non-destructive rewind** — restore files from any checkpoint without altering commit history
**Metadata stored separately** — all session data lives on the entire/checkpoints/v1 branch
Git Worktrees
Entire works seamlessly with git worktrees. Each worktree has independent session tracking, so you can run multiple AI sessions in different worktrees without conflicts.
Concurrent Sessions
Multiple AI sessions can run on the same commit. If you start a second session while another has uncommitted work, Entire warns you and tracks them separately. Both sessions' checkpoints are preserved and can be rewound independently.
Commands Reference
| Command | Description |
| ---------------- | ------------------------------------------------------------------------------------------------- |
| entire clean | Clean up orphaned Entire data |
| entire disable | Remove Entire hooks from repository |
| entire doctor | Fix or clean up stuck sessions |
| entire enable | Enable Entire in your repository |
| entire explain | Explain a session or commit |
| entire reset | Delete the shadow branch and session state for the current HEAD commit |
| entire resume | Switch to a branch, restore latest checkpointed session metadata, and show command(s) to continue |
| entire rewind | Rewind to a previous checkpoint |
| entire status | Show current session info |
| entire version | Show Entire CLI version |
entire enable Flags
| Flag | Description |
| ---------------------- | --------------------------------------------------------------------- |
| --agent <name> | AI agent to install hooks for: claude-code, gemini, or opencode |
| --force, -f | Force reinstall hooks (removes existing Entire hooks first) |
| --local | Write settings to settings.local.json instead of settings.json |
| --project | Write settings to settings.json even if it already exists |
| --skip-push-sessions | Disable automatic pushing of session logs on git push |
| --telemetry=false | Disable anonymous usage analytics |
**Examples:**
Configuration
Entire uses two configuration files in the .entire/ directory:
settings.json (Project Settings)
Shared across the team, typically committed to git:
settings.local.json (Local Settings)
Personal overrides, gitignored by default:
Configuration Options
| Option | Values | Description |
| ------------------------------------ | -------------------------------- | ---------------------------------------------------- |
| enabled | true, false | Enable/disable Entire |
| log_level | debug, info, warn, error | Logging verbosity |
| strategy_options.push_sessions | true, false | Auto-push entire/checkpoints/v1 branch on git push |
| strategy_options.summarize.enabled | true, false | Auto-generate AI summar…