Skip to main content
Replicas supports Muse Code through its native Muse Server Protocol (MSP).

​
Setup

​
API key

Create a key in the Meta developer console, then paste it under Muse Code → Muse API Key in Organization → Coding Agents or Personal → Coding Agents. See Credentials for scope and precedence.

​
Subscription

Install the Replicas CLI, sign in, and connect your Muse subscription:
The credential is personal by default. Run replicas muse-auth --org as an organization admin to share the subscription with your organization. See Credentials for scope and precedence.

​
Using Muse Code

Choose Muse Code from the workspace agent picker. Muse supports persistent sessions, streamed reasoning and tool activity, Plan Mode, model and thinking controls, image input, interruption, queued-message steering, interactive questions, workspace skills as slash commands, and /compact. If Muse requests tool approval, the chat shows the action and its available choices. Commands with multiple approval stages ask for each stage separately. muse-spark-1.2 is the default model; muse-spark-1.3 requires access on your subscription or API account. If it reaches a usage limit, Replicas can retry with another configured personal or organization Muse subscription or API key. See Fallback chains. Muse runs with full workspace permissions and does not support Replicas command-protection policies; Muse tabs show a warning for this limitation.

​
Programmatic use

Use muse anywhere Replicas accepts a coding-agent provider:
The API, MCP, Automations, and Defaults surfaces also accept muse.