Guides

Sign in to Muse Code for Helicon

Run muse login in the shell where Muse Code is installed. Helicon has no account and stores no credentials, so it uses the login the CLI already holds. If Helicon still reports that Muse Code is missing, the CLI is signed out in the shell or install Helicon is using.

Last updated 20 October 2026 · Markdown version

muse login

Run it in the shell where you installed Muse Code. On Windows that is PowerShell for a native install, or the WSL2 shell for a WSL2 install. Helicon uses your existing Muse Code subscription through this login. It needs no API key and adds no second bill.

On first run, muse asks you to authenticate. It offers browser sign-in or an API key.
Browser sign-in opens your web browser to approve the session, then returns you to the terminal.
Inside a running muse session, type /login to reopen the sign-in options.

When nobody is signed in, the home screen shows a Sign in to Muse card with the muse login command and a Check again button. The sidebar status also says Sign in to Muse.
Settings > Accounts lets you add named Muse profiles and sign in to each one without leaving the app. Helicon runs muse login under that profile and shows you the sign-in link and code to enter on Meta's page.
When Muse runs inside WSL, Accounts gives you the one command to run in a terminal instead.
If META_API_KEY is set, Helicon counts you as signed in and does not ask again.

Open the setup screen in Helicon and click Check again. It re runs detection without a restart. If it still fails, follow the steps in Fix: Helicon cannot find the muse CLI.

Native and WSL2 are separate installs on Windows. Each one needs its own muse login.
Remote daemon or SSH project: sign in on the machine that runs the daemon. Your laptop's login does not apply there.
Signed in with the wrong login: run muse logout, then muse login. Logout clears the stored browser session and any stored key.
Logout does not unset an exported META_API_KEY. Remove that variable from your shell profile or secret store too.

Sign in to Muse Code for Helicon

Open the shell where Muse Code is installed. On Windows, use PowerShell for a native install or the WSL2 shell for a WSL2 install. Each install needs its own login.
2
Sign in. Browser sign-in opens your browser to approve the session, then returns you to the terminal.
```
muse login
```
Confirm in Helicon. Open the setup screen and click Check again. Restart only if you changed PATH on Windows.
4
Sign out and back in if it still fails. Logout clears the stored browser session and any stored key. It does not unset META_API_KEY, so remove that from your shell too.
```
muse logout
muse login
```
5
For a remote daemon, sign in on that machine. Helicon uses the login on the machine that runs the daemon, so run muse login there once.
```
muse login
```

Frequently asked questions

Does Helicon need its own account or API key?

No to both. Helicon has no account and stores no credentials. It uses the login from muse login and your existing Muse Code subscription, with no second bill.

Why does Helicon say Muse Code is missing when it is installed?

An installed but signed-out CLI fails the same way as a missing one. Run muse login in the shell Helicon uses. The full fix is in Fix: Helicon cannot find the muse CLI.

Which login does a remote project use?

The one on the machine running the daemon. Local account profiles do not apply to SSH projects. See Muse Code over SSH.