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 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 sessions are created
After you enable Entire 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 |
| Find a session ID or see what is active | List Sessions |
| Inspect metadata, transcripts, or token usage from the terminal | Inspect Sessions in CLI |
| Attach missed session context | Attach Sessions |
| Continue previous agent work | Resume Sessions |
| Bring past local agent sessions into Entire | Import Past Sessions |
| Find prior session context by meaning | Semantic Search |
| Package context for another agent | Make Your Agent Use Entire |
Continue with
Sessions in Entire.io
Review timelines, transcripts, files, and attribution visually.
List Sessions
Find active sessions and session IDs from the terminal.
Attach Sessions
Recover missed context and link it to a checkpoint.
Resume Sessions
Continue prior agent work from a session or branch.
Import Past Sessions
Bring past local agent sessions into Entire as read-only checkpoints.
Troubleshooting
Resolve missing, stale, or unlinked sessions.