Muse Code Developer Docs

Two kinds of developer come here. If you are building an editor, a desktop app, an automation or an agent that drives Muse Code, start with Integrate. If you are adding capabilities to Muse Code itself, start with Extend. The user manual at dev.meta.ai/docs/muse-code covers installing and using Muse Code day to day.

Integrate with Muse Code

npm install @muse-code/sdk

Zero runtime dependencies; pair it with a muse binary and you have a client. A Python SDK is published as muse-code-sdk.

• Quickstart — the shortest complete path: start the host, run a turn, answer an approval, cancel, resume, and shut down, in TypeScript or Python. It walks the same program that runs against a release-built host on every change to the SDK and these docs.
• MSP concepts — the Muse Session Protocol (MSP) model: sessions, turns, commands and idempotency, approvals, resume, the item fold, and what host exit codes mean.
• MSP wire guide — the bytes: framing, the four frame shapes, ids, backpressure, the typed error vocabulary, and how to prove your client correct against the recorded transcript corpus.
• Cookbook — one tested recipe per task, each backed by a program that runs in CI.
• Wire protocol reference — one page per method, notification, error, type, capability and reserved identifier, generated from the schema bundle the server binary ships.
• SDK reference — the public @muse-code/sdk entry point, generated from its own source.

If you are writing a client in a language with no official SDK, the wire guide plus the schema bundle and the transcript corpus under schema/msp/ are your whole implementation surface.

Extend Muse Code

• Extending Muse Code — the overview: the four mechanisms, which one to use, and where each is configured.
• Skills — the SKILL.md format, where skills load from, and the muse skills command.
• Hooks — settings-level hooks: the hooks shape, matchers, and how a hook blocks or adds context.
• MCP servers — mcpServers entries for stdio and HTTP servers, credentials, and muse mcp login.
• Plugins — the overview: what a plugin packages, the two trust tiers, and which page to read next.
• Quickstart: your first plugin — a six-step walkthrough that builds, validates, installs and tests a small plugin.
• Plugin concepts — packages and capabilities, trust and review, hooks, MCP servers, marketplaces, other plugin formats, and plugins in SDK sessions.
• Plugin examples — five complete plugins on four pages, each shown file by file with the real commands and outputs that exercised it.
• Plugin reference — the manifest, the hook events and payloads, the muse plugins command and the validation diagnostics.

---

This site is a Developer Preview. Its pages are generated from commit 6a4ea794fed2ad356ff7f601df742d4779470e5e against schema fingerprint sha256:2db88d9ee93131257757ab3cf74026eab9079813a4cb82c45cc231901a170fc6 — the same fingerprint a server reports in its initialize result, so you can tell at a glance whether these pages describe the host you are talking to.