Mohamed Boudraandmillerben95
8332f4d1ff
* test(muse): record real host protocol fixtures * feat(muse): add built-in MSP provider Co-authored-by: millerben95 <millerben95@users.noreply.github.com> * fix(muse): expose provider settings in the app The daemon registered host settings without a client contribution, leaving sandbox, network, and workspace trust unreachable. Share the definition with a settings screen and expose it through Command Center even when installed plugins are disabled. * docs(muse): publish setup and provider support * test: correct runtime fixtures and restart readiness * fix(muse): hide reminder housekeeping from the timeline * fix(muse): use the official Muse Code mark Source: https://muse.ai/images/favicon/app-squiggle.svg Preserve the official silhouette path verbatim. Remove its gradient definition and use currentColor, scaling the original 100-unit coordinates into the 24-unit viewBox. Black silhouette renders match pixel-for-pixel. * fix(muse): adapt to current plugin APIs Use the screen API introduced with sidebar plugin items. Usage reports now come from source account discovery; remove the retired agent usage-reference request and headline marker, and exercise discovery through the existing provider fixtures. --------- Co-authored-by: millerben95 <millerben95@users.noreply.github.com>
2.8 KiB
title, description, nav, order, category
| title | description | nav | order | category |
|---|---|---|---|---|
| Muse Code | Install and configure Muse Code for Paseo. | Muse Code | 25 | Providers |
Muse Code
Run Meta's terminal coding agent in Paseo with your existing Muse installation and credentials.
Getting started
Install Muse Code on the machine running the Paseo daemon:
curl -fsSL https://dev.meta.ai/install.sh | sh
muse login
Use Muse 1.3.0 or newer. This integration was verified with 1.4.1. For API access, set
META_API_KEY in the daemon's environment instead of logging in. See
provider environment overrides.
In Paseo, select Muse Code, then choose a model, approval mode, and reasoning effort.
Paseo runs muse serve and communicates over the Muse Session Protocol (MSP). Your Muse
configuration determines the available models.
Plugin settings
Open Command Center and select Configure Muse Code. Changes apply when an agent's Muse host next opens, including a refresh of an existing agent.
| Setting | Default | Effect |
|---|---|---|
| Sandbox | On | Keeps Muse's filesystem and network sandbox enabled. Turning it off allows full network access. |
| Network | proxy-only |
Muse's sandbox network policy: proxy-only, restricted, or enabled. |
| Trust workspace | Off | Lets Muse load project-scoped skills and configuration. |
Approval modes control tool decisions separately: Default, Ask, Strict, and
Full access. Full access automatically allows escalated approval stages; it keeps the
sandbox setting you chose. Skills appear in the slash-command menu, alongside /compact.
Limitations in Muse 1.4.1
- Paseo MCP tools are unavailable. Muse drops the returned tool namespace before matching an MCP call. This upstream issue must be fixed in Muse before its agents can use Paseo tools.
- Compaction needs a model context limit. If your endpoint does not report one, configure
context_compaction.provider_context_limit_tokensin Muse for the selected model. - Usage windows appear only when Muse reports them. An empty
usage/readresponse leaves subscription usage unavailable. - Native subagents may need Muse's experimental SDK flag. Set
MUSE_EXPERIMENTAL_SDK_ENABLED=onin the provider environment if native subagent tools are missing. Linked child sessions appear only when Muse supplieschildSessionId.
See custom providers to override the binary or environment under
agents.providers.muse.