> ## Documentation Index
> Fetch the complete documentation index at: https://docs.entire.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Understand agent sessions, what they capture, and how they connect to checkpoints.

A [session](/glossary#session) is the complete record of an AI coding interaction: the prompts, responses, tool calls, file changes, metadata, token usage, and checkpoint links Entire captured while the agent worked.

Sessions show what the agent did, why it did it, and how the work came together.

## What sessions capture

Sessions can include:

* prompts and agent responses
* tool calls, shell commands, file reads, and file edits
* files created, modified, or deleted during the session
* agent, model, worktree, timing, and token metadata
* checkpoints and commits linked to the session
* line attribution showing how much of a change came from the agent versus a human

## How Sessions and Checkpoints Relate

Sessions and [checkpoints](/guides/checkpoints/overview) 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. |

Entire links these records so you can move from code, to checkpoint, to the session context behind it.

## How sessions are created

After you [enable Entire](/quickstart) for a repository, agent hooks capture session context while you work. When you commit, Entire can link the relevant session context to a checkpoint.

You can also attach a session later if capture started late, hooks did not fire, or the session was useful even though it did not produce file changes.

## What you can do with sessions

| 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) |
| 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                              | [Semantic Search](/guides/search/semantic-search/overview)          |
| Package context for another agent                                  | [Make Your Agent Use Entire](/learn/skills)                         |

## Continue with

<CardGroup cols={2}>
  <Card title="Sessions in Entire.io" icon="message" href="/guides/sessions/sessions-in-entire-io">
    Review timelines, transcripts, files, and attribution visually.
  </Card>

  <Card title="List Sessions" icon="list" href="/guides/sessions/list-sessions">
    Find active sessions and session IDs from the terminal.
  </Card>

  <Card title="Attach Sessions" icon="link" href="/guides/sessions/attach-sessions">
    Recover missed context and link it to a checkpoint.
  </Card>

  <Card title="Resume Sessions" icon="code-branch" href="/guides/sessions/resume-sessions">
    Continue prior agent work from a session or branch.
  </Card>

  <Card title="Import Past Sessions" icon="terminal" href="/guides/sessions/import-past-agent-history">
    Bring past local agent sessions into Entire as read-only checkpoints.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/guides/sessions/troubleshooting">
    Resolve missing, stale, or unlinked sessions.
  </Card>
</CardGroup>