--- title: "Helicon vs the muse terminal: Muse Code with a UI" url: https://helicon.sh/compare/muse-code-terminal description: "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." updated: 2026-09-19 site: Helicon --- # Helicon vs the muse terminal TUI The muse terminal TUI is the official way to run Muse Code and it stays the fastest path for a single task in one repo. Helicon is a desktop and web GUI over the same CLI: it adds persistent session history across projects, inline diffs, a visible approval queue and per thread cost, and it can resume sessions the TUI started. ## At a glance | | Helicon | The muse terminal | | --- | --- | --- | | Where it runs | Desktop app or browser against a daemon | Any terminal emulator | | Session history | Every session listed per project, resumable | Scrollback, until the tab closes | | Several repos at once | Sidebar grouped by working directory | One terminal tab per repo | | Diffs | Inline in the thread, where the edit happened | Patch text in the scroll | | Approvals | A queue you can see and act on | Inline prompt you have to be watching for | | Cost | Per thread, per day, per model at API rates | Not shown | | Offline setup | Needs the muse CLI installed and logged in | Is the muse CLI | | Who ships it | Community, MIT, unofficial | Meta, official | _Helicon compared with the muse terminal TUI._ ## What each one is The muse TUI is the interface that ships with Muse Code. You run `muse` in a directory, it starts a session in that working directory, and the whole conversation lives in that terminal tab. It is the reference implementation, it gets features first, and it is what every Muse Code doc assumes you are using. Helicon does not replace it. Helicon starts `muse serve` per workspace and speaks the Muse Code Session Protocol to it through Meta's MIT licensed SDK, which is the supported way to build a client. Your authentication stays in your own `muse login`. Both interfaces can be open at once against the same machine. ## Where they actually differ ### History survives the tab In the TUI, a session is as durable as the terminal it runs in. Close the tab or reboot and the thread is gone from view even when the underlying session still exists. Helicon keeps a local SQLite index of projects, sessions and turns, so every thread is one click away, including threads you started in the TUI. ### Parallel work has a home Running four agents means four terminal tabs and remembering which is which. Helicon groups threads by working directory, isolated git worktrees included, and shows which ones are running, which finished, and which are blocked on you. ### Approvals stop being a race A terminal approval prompt only helps if you are looking at that tab. Helicon surfaces every approval request as it arrives, maps onRequest, promptUnmatched and denyUnmatched one to one, and never batches or bypasses them. ### Diffs sit next to the sentence that caused them The TUI prints a patch. Helicon renders the edit as a diff in the thread at the point the agent made it, and opens the touched file in a viewer beside the conversation. ### You can see what the subscription did Helicon shows what each thread would have cost at Meta's published per token rates, broken down by day, model and thread. It is a meter reading, not a bill. The TUI does not surface this. ## Choose the muse terminal TUI if - You are doing one focused task in one repo and want zero extra software. - You are on a remote box over SSH with no desire to forward a port. - You want the first build of every new Muse Code feature, the day it ships. - You script Muse Code from CI or a Makefile, where a GUI has nothing to add. ## Choose Helicon if - You run several agent threads across repos and lose track of which needs you. - You want to reopen last Tuesday's session with its full history. - You are on Windows and want an installer rather than terminal plumbing. - You want approvals and costs visible instead of implied. ## Can you use both? Most people end up using both. Start a quick one off in the terminal, then open Helicon when you want the history, the diffs or the approval queue. Sessions started in the TUI show up in the Helicon sidebar automatically, and you can resume them there without losing context. ## Frequently asked questions ### Does Helicon replace the muse CLI? No. Helicon requires the muse CLI to be installed and logged in. It drives `muse serve` and speaks the Muse Code Session Protocol to it. If the CLI is not there, Helicon has nothing to talk to. ### Can Helicon see sessions I started in the terminal? Yes. The daemon discovers sessions for a workspace regardless of which interface started them, so TUI sessions appear in the sidebar with full history and can be resumed from the app. ### Is there a performance cost to running the GUI? Helicon runs one `muse serve` host per workspace, the same process the CLI would start. The UI is a Tauri window, and all state is local SQLite. The agent itself runs exactly as it would from the terminal. ## Related - [VS Code extensions](https://helicon.sh/compare/vs-code-extension): A standalone Muse Code desktop app compared with running the muse CLI inside VS Code: where an editor panel wins, where a separate session home wins, and how to run both. - [Zed with ACP](https://helicon.sh/compare/zed-acp): Running Muse Code inside Zed through an Agent Client Protocol bridge, compared with a standalone Muse Code desktop app. Editor native versus session native. - [JetBrains IDEs](https://helicon.sh/compare/jetbrains-acp): Muse Code inside IntelliJ, PyCharm, GoLand or WebStorm through an Agent Client Protocol plugin, compared with a standalone Muse Code desktop app. - [Claude Code desktop](https://helicon.sh/compare/claude-code-desktop): Two desktop apps for two different coding agents. What Helicon borrows from the Claude Code desktop experience, and what changes because the agent underneath is Muse Code. - [Codex app](https://helicon.sh/compare/codex-app): How a Muse Code desktop client compares with OpenAI's Codex app: same category, different agent, different billing, different openness. - [Cursor](https://helicon.sh/compare/cursor): Cursor is an AI editor with its own models and billing. Helicon is a window over the Muse Code CLI on your existing subscription. What each one is actually for. --- 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