Skip to content

Definition

What is the muse CLI?

The muse CLI is the command line tool that runs Muse Code. You install it, authenticate once with muse login, and then run muse inside a project to start a session. It holds your credentials, and every graphical client for Muse Code, including Helicon, drives this CLI rather than replacing it.

Last updated · Markdown version

The commands that matter

CommandWhat it does
museStarts an interactive session in the current directory
muse loginAuthenticates you. Credentials stay with the CLI
muse serveStarts a protocol host that other applications can drive
muse --versionConfirms the install is present and reachable

Why a GUI still needs it

A client like Helicon has no model, no account and no credentials. It starts muse serve and speaks the protocol to it, which means the agent, the subscription and the login are all the CLI's. If muse --version does not answer, the GUI has nothing to talk to.

Where credentials live

With the CLI, from your own muse login. Helicon never stores or handles them, which is the answer to the most common security question about wrapper clients.

Frequently asked questions

Do I need the CLI if I use a GUI?

Yes. Every Muse Code GUI drives the CLI. It is a requirement, not an alternative.

What does muse serve do?

It starts a host that speaks the Muse Code Session Protocol over JSON-RPC, which is how applications drive a session properly.

Where does muse login store credentials?

With the CLI itself. Clients like Helicon read nothing and store nothing.

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.