Definition
What is muse serve?
muse serve starts a Muse Code host that speaks the Muse Code Session Protocol over stdio instead of drawing a terminal interface. Applications launch it to drive sessions programmatically. Helicon starts one host per workspace, so each project directory gets its own process, exactly as the CLI would.
Last updated · Markdown version
One host per workspace
Sessions in Muse Code belong to a working directory, so Helicon runs one muse serve per project rather than one shared process. That keeps isolation honest, including for git worktrees, which are separate directories over the same repository.
What it is not
- Not a network server you expose. It speaks over stdio to the process that launched it.
- Not a second agent. It is the same Muse Code, without the terminal interface.
- Not a place credentials live. Authentication is still your own
muse login.
Source: Muse Code (Meta Model API docs, session protocol section)
Frequently asked questions
Does muse serve replace muse?
No. It is the same tool exposing a protocol instead of a terminal interface, for applications to drive.
How many hosts does Helicon run?
One per workspace you add, which is the same process the CLI would start for that directory.
Can I run muse serve myself?
Yes. It is a normal CLI command, and any MSP client can drive it.
Keep reading
- the Muse Code Session ProtocolMSP is the JSON-RPC protocol that applications use to drive a Muse Code session over stdio, instead of parsing terminal output. What it carries and why it matters.
- the muse CLIThe muse command line tool is how you run Muse Code. What it installs, what muse login does, and why a GUI still needs it present.
- Remote daemon and web UIThe same Helicon UI ships as a web app pointed at a daemon on another machine, so a laptop can supervise Muse Code running on a workstation or a server.
- the Agent Client ProtocolACP is a general protocol that lets editors talk to any conforming coding agent. How it differs from a Muse Code specific protocol, and what gets lost in the bridge.
- an ADEAn ADE is the workspace you supervise coding agents from, the way an IDE is the workspace you write code in. What belongs in one and what does not.
- agent approvalsAn approval is the moment an agent asks before acting. The three Muse Code modes, what each one does, and why bypassing them is the wrong optimisation.
Same Muse Code. Same subscription. Better interface.
Free and MIT licensed. Windows installer, Apple Silicon, Intel and universal macOS DMGs, and a web build against a daemon you run.