Skip to main content
View and manage agent sessions tracked by Entire.
entire session is also available as entire sessions.

​
Session Lifecycle

The diagram shows the paths through a session workflow. entire session info reports live sessions as active or ended. Stale, resumed, adopted, attached, and imported describe a session’s condition or how its context entered Entire:

​
session current

Show the session running this command, or the most recent one in this worktree. When an agent runs this command, Entire reports that agent’s own session, read from the session ID the agent publishes into the environment of the commands it runs. Failing that, it falls back to the most recently active session in this worktree, and then to the most recent one anywhere in the repository’s shared session store. The output says which one you got: the Resolved line in text mode, or the resolution field with --json. Only caller-env and ancestry identify the session running the command; other-worktree can be any unrelated session, because every worktree of a repository shares one store. Check it before acting on the session.

​
session list

List all sessions tracked by Entire, including ended sessions.
For active sessions only, use entire status.

​
session info

Show detailed information for a specific session. entire session info shows agent, model, status, worktree, timing, token usage, checkpoint linkage, and files touched.

​
session tokens

Show token usage and optimization recommendations for a session.
When you omit the session ID, Entire identifies the calling agent’s session from agent session IDs and process ancestry, falling back to the most recently active session in this worktree and then elsewhere in the repository. The report says how the session was resolved, and ambiguous or cross-worktree matches also print a warning on standard error.

​
session stop

Stop one or more active sessions.
entire session stop marks sessions as ended. It does not create a checkpoint or flush pending work. Commit first when you want Entire to link session context to code changes.

​
session attach

Attach an existing agent session that Entire did not capture automatically.
This command reads the session transcript, creates or updates a checkpoint, and links it to the latest commit. Use it if you started the session before installing hooks, the hooks did not fire, or you want to preserve a research session. If the latest commit already has an Entire-Checkpoint trailer, Entire adds the session to that checkpoint. Otherwise, Entire creates a checkpoint and offers to amend the commit with the trailer.
entire session attach requires at least one commit in the repository. If Entire cannot locate the transcript for the selected agent, it tries to detect the agent from known transcript locations.

​
session adopt

Adopt an active session from another worktree into the current repository.
Use this command when an agent starts in one repository or worktree, then moves and makes changes in another.

​
session resume

Resume an agent session from a branch or interactive picker.
With no argument, Entire opens an interactive picker of stopped sessions across all worktrees. After you select a session, Entire checks out its branch, restores the session log, and asks whether to start the agent. With a branch argument, Entire:
  1. Checks out the specified branch.
  2. Finds the session ID from commits unique to the branch.
  3. Restores the session log if it does not exist locally.
  4. Asks whether to start the agent in an interactive terminal or prints the resume command in a terminal without interactive input.
If the branch exists on the remote but not locally, Entire prompts you to fetch it.
If the branch contains newer commits without checkpoints, Entire can reset Git state to the most recent commit with a checkpoint. Entire prompts before continuing unless you use --force.