Skip to content
Muse Code Developer Docs
Developer Preview

Muse Code Developer Docs

Build a client for Muse Code using the Muse Session Protocol, in TypeScript or in any language.
Run the quickstartStart with the conceptsBuild from the wire upBrowse the reference
Terminal window
npm install @muse-code/sdk

Zero runtime dependencies; pair it with a muse binary and you have a client.

Where to start

Section titled “Where to start”
  • MSP concepts — the 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.
  • 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.

For a runnable first session in TypeScript, start with the Quickstart: it walks the same program that runs against a release-built host on every change to the SDK and these docs, so every step on it is one that host satisfies today.

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.

This site is a Developer Preview. Its pages are generated from commit 36e29c15c8c300cb18da01808eb554d934505f6c against schema fingerprint sha256:577d717d09bf3aae6ad43c85d3c2d8e0c37bbde350897c94808626d2f362060c — 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.