How do I find, resume or branch a past session?

Sessions and history

Every session Muster opens is a real CLI session, and the CLI writes its own transcript to disk. Muster indexes those transcripts, which is how the panel on the right knows what a session did without Muster spending a token of its own.

Finding a session

The session list shows the sessions for the open project, most recent first, with the title the CLI gave it and the tokens it has used. Search (⌘P) goes further: it covers past conversations, not just files, so “where did an agent touch the retry logic” is a question with an answer.

Resuming

A session is on disk, so closing the app does not end it. Resume reopens it where it stopped, with its context intact.

A session that has gone dormant says so in its pane, with how many messages it kept, and offers to resume rather than resuming silently — restarting a large context costs tokens, and spending them should be your decision.

Branching

Branch, next to Resume, forks a session: the conversation is copied into a new session that starts from the same point. It replaces the focused terminal pane, or opens a new tab when there is no target.

Branching takes the whole conversation, not a summary of it. An earlier version seeded the branch with a summary and it was reverted: the summary was worse context than the conversation it replaced.

The branch also takes the CLI’s own task list with it. That list lives outside the transcript, and --fork-session does not copy it — so a branch used to start talking about a list it did not have.

Handoff

Write handoff generates SESSION_HANDOFF.md in the project root, assembled from the transcript and from git. It spends no tokens: it is written by reading, not by asking the model.

It is the cheap way to end a session you do not want to keep paying to carry.

Next

Sessions cost usage, and usage has a window: The 5-hour window.