Overview

Entire keeps two connected records of AI-assisted work. A session is the conversation: the prompts, responses, tool calls, and file changes that happen while an agent works. A checkpoint is the individual unit of that context, saved when you commit and linked to the commit. Entire captures both automatically and stores them alongside your commits in the repository, so nothing is lost when a terminal closes or a conversation ends.

​

What Is a Session?

A session is the complete record of a coding interaction between you and your AI agent. It captures:

• prompts and agent responses
• tool calls, shell commands, and file operations
• files created, modified, or deleted
• time-stamped agent and model metadata
• line attribution showing which changes came from the agent versus a human.

​

What Is a Checkpoint?

A checkpoint is the individual unit of context within a session behind an AI-assisted change. When you or your agent commit, Entire saves the captured session context, such as the prompts, transcript, and tool calls that led to the commit, as a checkpoint and links it to that commit. Each checkpoint has an ID, and Entire adds it to the commit message with an Entire-Checkpoint trailer. A single session can produce many checkpoints, one for each commit you make while it runs. A single checkpoint can also draw on more than one session when several contributed to the same change. See How Sessions and Checkpoints Relate for the common shapes. A checkpoint stores the available context behind the change, including:

• the linked Git commit
• the agent session or sessions behind the change
• prompts and transcript
• tool activity
• changed files
• token usage, when available
• AI attribution for the changed lines

​

How Sessions and Checkpoints Relate

Sessions and checkpoints have a flexible relationship that mirrors how you actually work:

​

How It Works

Once you enable Entire for a repository, the CLI uses Git hooks and agent hooks to capture session context while you work. When you commit, Entire saves that context as a checkpoint and links it to the commit. In practice, you just work, commit, and the context follows along. See Capture Sessions and Their Checkpoints for setup details and commit-linking options. If capture started late, hooks did not fire, or a session was useful even though it did not produce file changes, you can attach the session to a checkpoint after the fact.

​

Why This Helps

• Resuming exactly where you left off. Pick up prior agent work from a session or a branch instead of starting over. See Resume Sessions.
• Seeing what actually happened. Review prompts, transcripts, tool calls, and file changes for any session without guessing. Read more on Sessions in entire.io and Inspect Sessions in CLI.
• Tracing any commit back to the conversation that produced it. Every commit made during a session is linked to a checkpoint, so you can go from code to context easily. See Inspect Checkpoints.
• Knowing who wrote what. Line attribution shows how much of a change came from the agent versus a human.
• Recovering missed context. Attach a session after the fact if capture started late or hooks didn’t start. See Attach Sessions.
• Bringing in past work. Import agent history that predates Entire, and find prior context by meaning across past sessions. Read more on Search.

​

How Checkpoints Connect to Git

Entire stores checkpoint metadata in your repository, in its own Git ref or on the checkpoints branch depending on the storage backend. Your normal Git history stays clean. Entire does not add extra commits to your working branch.

​

Get Started

​

Continue With