No active session appears
Check repository and hook status:The session did not link to a commit
A normal committed checkpoint needs both captured session context and a Git commit. If the session exists but was not linked, attach it to the latest commit:Entire-Checkpoint trailer.
The session is attached to the wrong worktree
If an agent started in one worktree and continued in another, adopt the session into the current repository:Stale sessions keep showing up
Useentire status to find active and stale sessions. If a session is no longer running, stop it:
Token usage is missing
Token usage depends on what the agent exposes and when the session data is available. Some agents only expose full token usage after the session ends. Check the session details first:The raw transcript is missing
Entire reads transcript data from the agent’s session storage. If the agent deleted or moved its local transcript, Entire may still have metadata but not the raw transcript bytes. Try:Continue with
List Sessions
Find active sessions and session IDs.
Attach Sessions
Recover missed context and link it to a checkpoint.
Resume Sessions
Continue previous agent work from a session or branch.
Stop Sessions
End stale or active sessions.