> ## Documentation Index > Fetch the complete documentation index at: https://docs.entire.com/llms.txt > Use this file to discover all available pages before exploring further. # Overview > Enable Entire and automatically store your agent sessions in Git on every push. [Entire 101 | Ep. 2: How to Create Your First Checkpoint](https://www.youtube.com/embed/ehWDtXYFZ2Y) Entire keeps two connected records of AI-assisted work. A [session](/glossary#session) is the conversation: the prompts, responses, tool calls, and file changes that happen while an agent works. A [checkpoint](/glossary#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 unit of context Entire saves 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](/glossary#entire-checkpoint). 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](#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](/guides/sessions/sessions-in-entire-io#files-and-attribution) for the changed lines ## How Sessions and Checkpoints Relate Sessions and checkpoints have a flexible relationship that mirrors how you actually work: | Scenario | How it looks in Entire | | - | - | | One session, one checkpoint | Most common. You ask the agent to do something, it does the work, and you commit. | | One checkpoint, multiple sessions | Several sessions contribute to the same change before you commit. | | One session, multiple checkpoints | One longer session keeps going while you commit multiple checkpoints along the way. | | Multiple sessions, multiple checkpoints | Multiple sessions and commits are linked across a larger or parallel piece of work. | ## How It Works Once you [enable Entire](/quickstart) for a repository, the [CLI](/cli-reference) uses Git hooks and [agent hooks](/agents/overview) 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](/guides/checkpoints/capture-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](/guides/sessions/attach-sessions) 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](/guides/sessions/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](/guides/sessions/sessions-in-entire-io) and [Inspect Sessions in CLI](/guides/sessions/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](/guides/checkpoints/inspect-checkpoints). * Knowing who wrote what. Line attribution shows how much of a change came from the agent versus a human. See [entire blame](/cli-reference/blame). * Recovering missed context. Attach a session after the fact if capture started late or hooks didn't start. See [Attach Sessions](/guides/sessions/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](/guides/search/overview). ## How Checkpoints Connect to Git Entire stores checkpoint metadata [in your repository](/security#where-your-data-lives), in its own Git ref or on the checkpoints branch depending on the [storage backend](/guides/checkpoints/checkpoint-storage). Your normal Git history stays clean. Entire does not add extra commits to your working branch. ## Get Started | Task | Where to go | | - | - | | Review prompts, transcript, tools, files, and attribution visually | [Sessions in entire.io](/guides/sessions/sessions-in-entire-io) | | Find a session ID or see what is active | [List Sessions](/guides/sessions/list-sessions) | | Inspect metadata, transcripts, or token usage from the terminal | [Inspect Sessions in CLI](/guides/sessions/inspect-sessions-in-cli) | | Open a checkpoint from the CLI or entire.io | [Inspect Checkpoints](/guides/checkpoints/inspect-checkpoints) | | Control when and how sessions and checkpoints are captured | [Capture Sessions and Their Checkpoints](/guides/checkpoints/capture-checkpoints) | | Choose where checkpoint data is stored | [Storage Backends](/guides/checkpoints/checkpoint-storage) | | Attach missed session context | [Attach Sessions](/guides/sessions/attach-sessions) | | Continue previous agent work | [Resume Sessions](/guides/sessions/resume-sessions) | | Bring past local agent sessions into Entire | [Import Past Sessions](/guides/sessions/import-past-agent-history) | | Find prior session context by meaning | [Search](/guides/search/overview) | | Package context for another agent | [Make Your Agent Use Entire](/learn/skills) | ## Continue With > **[Sessions in entire.io](/guides/sessions/sessions-in-entire-io)** > > Review timelines, transcripts, files, and attribution visually. > **[Inspect Checkpoints](/guides/checkpoints/inspect-checkpoints)** > > Open a checkpoint from the CLI or entire.io. > **[List Sessions](/guides/sessions/list-sessions)** > > Find active sessions and session IDs from the terminal. > **[Attach Sessions](/guides/sessions/attach-sessions)** > > Recover missed context and link it to a checkpoint. > **[Resume Sessions](/guides/sessions/resume-sessions)** > > Continue prior agent work from a session or branch. > **[Storage Backends](/guides/checkpoints/checkpoint-storage)** > > Choose between a Git ref and the checkpoints branch. > **[Investigate Why Code Exists](/learn/investigate-why-code-exists)** > > Use attribution and checkpoint context to investigate a surprising line. > **[Troubleshooting](/guides/sessions/troubleshooting)** > > Resolve missing, stale, or unlinked sessions and checkpoints.