Sessions: resume, continue, branch and history management

You will name a session, resume it and explore a conversation branch without assuming files were rolled back. Examples are illustrations.

Sources checked September 30, 2026 describe locally saved sessions tied to working directories. Resuming restores conversation continuity; current files and Git branch still need inspection. A conversation branch is not a Git branch or isolated worktree.

Before leaving:

Summarize the current practice task: inspected files, completed changes,
actual test results, remaining questions and unapproved actions.
Do not make further edits.

Give the session a meaningful name through /rename if available. Keep secrets out of titles and summaries. Record the working directory and repository branch separately.

Illustrative stopping point:

Task: course-list toggle.
Changed: index.html.
Checked: two clicks; keyboard check still pending.
Remaining: verify keyboard and narrow layout.
Not approved: PR or publication.

Compare to the actual file and tests. A summary is not the source of truth.

From the same practice directory:

claude --continue

This continues the recent session for the directory. To select among sessions:

claude --resume

Inside an interactive session, /resume opens the picker. Inspect session title, directory and relevant history before selecting. The source describes default worktree scoping and options to widen search; wider listings do not mean every session belongs to the current code checkout.

We are resuming. First inspect the current practice file and report differences
from the stopping summary. Do not edit yet.
Confirm the remaining tests and ask before changing scope.

If someone edited the file meanwhile, current code can differ from old history. Do not execute the old plan unchanged. Git branch switching changes visible files without rewriting the conversation's past facts.

The documented /branch or --fork-session creates a new conversation identity with copied history. It does not automatically give separate files.

For this exercise, compare an alternative plan without writing:

Propose an alternative button label only.
Keep it as a proposal; do not edit files or switch Git branches.

Use a separate worktree before parallel writing, covered later. Do not open the same session in two terminals for competing edits without understanding coordination.

Local session records can contain source text, tool outputs and private material. Closing the terminal is not automatic deletion. Use the documented local-data controls and organization policy when cleanup is required. Never share a raw transcript casually.

Archiving, deleting conversations, restoring file checkpoints and Git restoration are different operations. Do not delete a session to undo a code change.

Easy: find the correct session

Name and resume it. Success: matching directory, task and history.

Intermediate: changed file

Modify a harmless source copy outside the session, then resume read-only. Success: identify current differences before acting.

Challenging: alternative without collision

Branch a conversation and request a plan only. Success: understand no filesystem isolation was created.

Wrong recent session: use the picker and inspect context rather than trusting --continue blindly.

History differs from code: re-read current files and branch.

Missing session: check directory, worktree scope and local account/environment before declaring it gone.

Two writers collide: stop, inspect diff and separate workspaces before continuing.

Need restoration: use the tool matching what must be restored, not session deletion.