Helios / User guide / Muse Code on Linux
Muse Code on Linux
Install Meta Muse Code and connect it to Helios through muse serve, with account checks, API-key precedence and background-work guidance.
Helios 0.114.4 · Source reference ↗
Install Meta Muse Code
Install the native muse CLI using Meta’s Muse Code instructions. Verify and sign in from a terminal:
muse --version
muse login
Complete the native Meta-account flow. Helios starts muse serve and uses its native protocol for conversations, approvals and activity.
Check the authentication route
Open Settings → Accounts to inspect Muse’s reported identity and status. Settings can open the same native sign-in flow.
The Muse provider page can pass a Meta API key to muse auth set --provider meta --api-key-stdin; Muse stores that credential and Helios keeps no copy.
An environment META_API_KEY takes precedence over stored account sign-in. Check whether the intended route is an account allowance or a metered API key before sending work.
Refresh and choose a model
Refresh Muse under Settings → Providers after login or a CLI update. Choose from the models the runtime reports. Model availability and reasoning controls depend on the signed-in account and installed CLI.
Start a chat in a project folder, ask for a small read-only explanation and verify the answer. Use Ctrl+Enter to send.
Follow native questions and background work
Muse supports native questions, approvals, session continuation and reported background activity. Answer the current dialog, including a typed response when appropriate. A settled or withdrawn question cannot be answered through an old dialog.
The Background pane can list Muse activity. Its available controls differ from Claude’s; do not expect an Output action for every Muse row. Native goal updates can be reflected in the Work and conversation controls.
Know what differs
Muse permission choices map to MSP, and the sandbox posture is set when its process starts. Changing a label in a live conversation should not be treated as rebuilding its process sandbox.
Native image conversion and supported Helios browser tools are available. A general message-level conversation fork and the generic safe Revert action are not exposed for this route.
Use the provider’s own usage reporting. Helios does not establish an equivalent universal dollar or token breaker for Muse; see budget scope.