Glossary

38 terms

Glossary term	Definition
Agent	An AI coding assistant connected to Entire, such as Claude Code, Codex, Cursor, Factory, Gemini CLI, GitHub Copilot CLI, OpenCode, or Pi.
Agent run	One execution of an agent inside a session. Entire compares your work before each run with the agent’s changes so line attribution can stay accurate.
Checkpoint	A save point for your work. Entire creates checkpoints around agent activity and links committed ones to Git commits.
Checkpoint ID	The identifier for a checkpoint, shown in the CLI and entire.io. The format follows the storage backend: ref-based storage, the default, uses a 26-character time-sortable ULID such as `01KVBJCWYA4YW6J5M9GP655HZN`; branch-based storage uses 12 hexadecimal characters such as `8a513f56ed70`.
Checkpoint linking	The connection between a Git commit and the Entire checkpoint that captured the session context behind it.
Checkpoint ref	The Git ref that holds one checkpoint under the ref-based backend, at `refs/entire/checkpoints/<shard>/<id>`. List them with `git for-each-ref refs/entire/checkpoints/`.
Checkpoint remote	A Git remote that holds checkpoint metadata separately from your code remote. By default, Entire pushes checkpoint metadata to your code remote.
Checkpoint storage backend	How Git organizes checkpoints in your repository. `git-refs` writes one checkpoint ref per checkpoint and is the default for repositories enabled with CLI 0.10.0 or later. `git-branch` writes all of them to the checkpoints branch. See Session Storage.
Checkpoints branch	The Git branch where Entire stores checkpoint and session metadata under the branch-based backend. Entire names the branch `entire/checkpoints/v1`.
Code Search	A literal search over the text of tracked files on a repository’s indexed branch, returning the files and lines that contain a match. Run `entire search --code`, or open the Code tab in entire.io.
Commit trailer	Structured metadata that Entire appends to a Git commit message, such as `Entire-Checkpoint` and `Entire-Attribution`.
Committed checkpoint	A checkpoint that Entire has linked to a Git commit and written to checkpoint storage.
Dispatch	A markdown summary of recent agent work across one or more repositories, branches, and time windows.
Entire CLI	The command line tool that records sessions, creates checkpoints, links commits, and syncs metadata.
entire.io	The web interface for searching and browsing repositories, sessions, checkpoints, dispatches, and agent activity captured by Entire.
Entire Repository	A Git repository that EntireDB serves. Entire can host the repository or connect it to an upstream GitHub repository through one or more mirror placements.
Entire-Attribution	A commit trailer that records how much of a commit came from the agent versus a human.
Entire-Checkpoint	A commit trailer that records the checkpoint ID associated with a commit.
Finding	A single issue a review runner raises against a branch or trail, such as a bug, a regression, or a missing test. Open findings block the trail from merging until you resolve or dismiss each one.
Line attribution	Entire’s calculation of how many changed lines in a commit came from the agent and how many came from a human.
Metadata	Structured data Entire records about sessions and checkpoints, including timestamps, agent type, token usage, attribution, and configuration.
Mirror	A connection between a GitHub repository and Entire. GitHub remains the upstream repository, while Entire serves Git traffic through one or more regional mirror placements.
Mirror placement	A copy of a GitHub-backed repository on one EntireDB cluster. Each placement has its own cluster, status, and `entire://` URL.
Nested session	A child session created when an agent spawns another agent or sub-agent during the same body of work.
Plugin	An executable named `entire-<name>` on your `$PATH` that adds a command to the Entire CLI. Running `entire <name>` dispatches to it. Distinct from a skill, which teaches an agent to use Entire in natural language.
Repository object	The control-plane record that identifies an Entire Repository and stores metadata such as its owning project, visibility, and placement information. The `entire repo` commands manage these objects.
Runner	A config-driven job that runs an AI coding agent in an isolated cloud sandbox against a branch or trail. You define runners per repository in `.entire/runners/`. They produce Entire’s automated review signals, including review comments, summaries, and scores for risk, drift, confidence, and security.
Search	Entire’s search over every indexed repository you can access, covering both semantic search and Code Search so one query returns the code and the work behind it. See the Search overview.
Semantic search	A search over indexed Entire history that matches by phrase, meaning, or agent context rather than by exact words, returning related commits and sessions. Its literal counterpart is Code Search.
Session	A complete interaction with an AI coding agent from start to finish. Sessions include prompts, responses, code changes, checkpoints, token usage, metadata, and line attribution.
Session branch	A Git branch that holds captured session data without adding commits to your working branch.
Session context	The prompts, responses, tool activity, code changes, and metadata that explain what happened during a session.
Shadow branch	A temporary local branch that holds checkpoints during active sessions. Entire names shadow branches like `entire/<commit>-<worktree>` and does not push them to remote repositories.
Skill	A reusable workflow that helps an agent use Entire history, checkpoints, and session context for a specific task.
Token usage	Counts of input tokens, output tokens, cache creation tokens, cache reads, and API calls recorded for a checkpoint or session.
Trail	Entire’s unit of work, covering one branch and one pull request from one intent to shipped code. A trail groups that intent, the checkpoints recorded along the way, and a rolled-up summary and report. Teams review the trail instead of the raw diff.
Worktree ID	An opaque identifier Entire puts in a shadow branch name to tell active worktrees apart.

Getting Started

Guides

Security

Resources