Skip to main content
Sessions are complete records of your AI coding interactions. The Entire web app provides tools to browse, search, and understand your session history.
Session details

​
Checkpoints and Sessions

Checkpoints and sessions have a many-to-many relationship depending on the developer’s workflow. Here are the scenarios:
  1. Single checkpoint, single session - The most common workflow. You ask Claude Code to implement a feature, it does it and then you create a commit and push it.
  2. Single checkpoint, multiple sessions - A developer might have multiple Claude Code sessions working on a single feature and once done, the developer pushes a single checkpoint.
  3. Multiple checkpoints, single session - A developer might have a single session running in a terminal while creating multiple commits throughout that session and thereby creating multiple checkpoints. Entire will match up these checkpoints to the single session.
  4. Multiple checkpoints, multiple sessions - A developer might have multiple terminals with multiple sessions and checkpoints.

​
Viewing Sessions

Click on a checkpoint to view it’s sessions. Each session card shows:
  • Date and time - When the session occurred
  • Duration - How long the session lasted
  • Steps - How many steps the conversation took between the user and agent
  • Tool Calls - How many tools were called
Tool calls
  • Token usage - Total tokens consumed
  • Attribution - The percentage breakdown between AI Agents and Humans who contributed to the code See a breakdown of who wrote the code: agent vs. human.
Line attribution
  • Your prompts - What you asked the AI
  • AI responses - What the agent replied
Conversation transcripts help during code review—reviewers can see the reasoning behind changes.

​
File Tab View

Line attribution
See all code changes made during the session:
  • Files modified - List of changed files
  • Diff view - Side-by-side or unified diff
  • Checkpoint breakdown - Which checkpoint made which changes

​
Nested Sessions

When an AI agent spawns sub-agents, Entire captures these as nested sessions. The session view shows:
  • Parent session - The main session
  • Child sessions - Sub-agent sessions, indented in the timeline
  • Aggregated stats - Combined token usage across all sessions
Click on a child session to view it in isolation, or expand it inline to see how it fits into the parent session.

​
Linking to Commits

Sessions are linked to Git commits via checkpoint IDs. In the session view:
  • Click on a checkpoint to see its associated commit
  • Click on a commit hash to view it on GitHub
  • The commit message shows the Entire-Checkpoint trailer
This bidirectional linking makes it easy to navigate between sessions and your Git history