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:
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 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
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.