Features
Session history and resume
Helicon keeps a local index of every Muse Code session on the machine, grouped by the working directory the agent ran in. Each session keeps its full turn history and resumes in one click, including sessions you started in the muse terminal TUI, so closing a terminal tab no longer loses the thread.
Last updated · Markdown version
The problem this solves
In a terminal, a session is as durable as the tab it runs in. Close the tab, reboot, or lose the SSH connection and the conversation is gone from view even though the underlying session still exists on disk. Anyone running more than one agent at a time hits this within a day.
How Helicon indexes sessions
- A local daemon starts one
muse servehost per workspace and speaks the Muse Code Session Protocol to it. - Projects, sessions and turns are written to local SQLite on your own machine.
- Projects are keyed by the working directory the agent ran in, so isolated git worktrees appear as their own entries with a badge.
- Sessions the terminal TUI created are discovered by the daemon, not scraped from output, so they carry their real history.
What resuming actually restores
- Every turn in order, with the model and reasoning effort each one used.
- Tool calls and their output, including commands the agent ran.
- Inline diffs at the point in the thread where the edit happened.
- Approval decisions, so you can see what you allowed and when.
- Cost for the thread at published per token rates.
Finding a thread again
The sidebar groups sessions under their project. The command palette jumps to any project, session or action without the mouse. If you remember the repository, you are two keystrokes from the thread.
Frequently asked questions
Does Helicon see sessions I started in the terminal?
Yes. The daemon discovers sessions for a workspace regardless of which client started them, so terminal TUI sessions appear in the sidebar with full history and resume from the app.
Where is session history stored?
In local SQLite on your machine. Helicon has no server side account and syncs nothing.
Can I resume a session after rebooting?
Yes. History is on disk, so a restart does not lose anything.
Keep reading
- Projects and worktreesHelicon groups every Muse Code thread under the directory the agent worked in, isolated git worktrees included, so parallel work across repositories has one place to live.
- Keyboard and paletteA 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 terminalHow 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.
Same Muse Code. Same subscription. Better interface.
Free and MIT licensed. Signed Windows installer, universal macOS DMG, and a web build against a daemon you run.