muse-acp

Use your existing Muse Code subscription in Zed, IntelliJ IDEA, and other
JetBrains IDEs.

muse-acp is a small, dependency-free Rust bridge between the
Agent Client Protocol (ACP) used by editors
and Muse Code's native Muse Session Protocol
(MSP). It ships as one native binary—no Node.js, npm, or Python runtime needed.

This project started from a simple itch: I wanted to use the Muse Code
subscription I already pay for inside the editors I already use, while keeping
Muse's session engine, tools, authentication, and approval flow.

muse-acp is an independent community project. Muse Code and Muse Spark are
products of Meta and are not affiliated with or supported by this project.

See ROADMAP.md for protocol-compatibility, reliability, feature,
and release priorities.
The MSP event compatibility matrix records the
ACP mapping or intentional disposition of every notification in the pinned
schema, plus observed host extensions and server-initiated requests.

Why MSP instead of muse exec?

muse-acp starts one long-lived muse serve process and translates between
ACP and MSP for the lifetime of the editor. Sessions, streamed updates,
cancellation, configuration, approvals, and resume behavior travel over Muse's
native protocol without starting a new Muse CLI process for every prompt.

Other thoughtful integrations make a different, pragmatic choice:
bex-co/muse-code-acp and the
muse-codes Rust SDK
wrap the headless muse exec --json event stream. That approach is useful for
one-shot automation and broad compatibility. This project is optimized for a
stateful IDE session, so MSP is the more direct fit.

Quick start

1. Install Muse Code

You need [Mus