---
title: "How to resume a Muse Code session you started earlier"
url: https://helicon.sh/guides/resume-a-muse-session
description: "Find and reopen any past Muse Code thread, including ones started in the terminal TUI, with its full history, diffs and approval record intact."
updated: 2026-09-19
site: Helicon
---

# Resume a Muse Code session

Open Helicon, find the project in the sidebar, and pick the session. The thread reopens with every turn, tool call, diff and approval in place, and you can carry on from there. Sessions started in the muse terminal TUI are discovered by the daemon and resume the same way.

## Where sessions come from

Helicon's daemon runs one `muse serve` host per workspace and indexes what that workspace has: projects, sessions and turns, in local SQLite. It does not matter which client created a session. If Muse Code has it on disk for that directory, Helicon lists it.

## Three ways to find one

1. The sidebar, grouped by working directory, with worktrees as their own entries.
2. The command palette, which searches projects and sessions by name.
3. The project home, which puts recent work for that project next to the composer.

## What comes back

- Every turn in order, with the model and reasoning effort it used.
- Tool calls and their output.
- Inline diffs at the point the edit happened.
- Approval decisions, so the record of what you allowed survives.
- Cost for the thread at published per token rates.

## Resume a Muse Code session in Helicon

1. **Open Helicon** The sidebar lists projects by working directory.
2. **Find the project** Use the sidebar, or the command palette to search by name.
3. **Pick the session** Sessions are listed under their project with their history.
4. **Carry on** Type in the composer. The thread continues where it stopped.

## Frequently asked questions

### Can I resume a session I started in the terminal?

Yes. The daemon discovers sessions for the workspace no matter which client started them.

### Does resuming cost anything extra?

It uses your Muse Code subscription like any other turn. Helicon shows what the thread would have cost at published rates.

### What if the project moved on disk?

Sessions are keyed by working directory, so add the new path as a project. The old entry stays until you remove it.

## Related

- [Session history and resume](https://helicon.sh/features/session-history): Every Muse Code session, grouped by project, with full history and one click resume. Sessions started in the muse terminal TUI are discovered and resumable too.
- [Keyboard and palette](https://helicon.sh/features/command-palette): A command palette, slash commands and a model and reasoning effort picker. Every project, session and action in Helicon is reachable without the mouse.
- [The muse terminal](https://helicon.sh/compare/muse-code-terminal): How a Muse Code GUI differs from the muse CLI terminal interface: session history, inline diffs, approvals and cost, side by side with what the TUI already does well.

---

Helicon is a free, MIT licensed, unofficial community client for Meta's Muse Code CLI. Not made, sponsored or endorsed by Meta. Source: https://helicon.sh/. Machine readable index: https://helicon.sh/llms.txt