Skip to main content

muse-code-sdk

The Python SDK for Muse Code: an asyncio-first client for driving a Muse Code agent over the Muse Session Protocol (MSP), with a thin synchronous wrapper for scripts and notebooks.

  • Open and resume sessions against a spawned muse serve host, or attach to one you already run.
  • Stream a turn's items and text deltas as async iterators; await the turn's server-authored outcome.
  • Answer tool-approval requests with a handler you register, or pass it as ResumeSessionOptions(on_approval=...), with on_approval_error=... for its failures, so approvals still pending at resume reach it.
  • Answer the agent's questions: list them with session.fold.pending_user_inputs() and answer with session.answer_user_input.
  • A client-side fold keeps a live, typed view of the session — items, session state, pending commands — with gap recovery after reconnects, and safe same-command retry that can never double-submit.
  • SyncMuseClient mirrors the same surface with blocking verbs.

Status: developer preview. Experimental protocol surfaces may change.

The generated MSP wire types live in the companion package muse-code-msp and are never restated here; it is installed with this package, pinned to the same version. One further runtime dependency: pydantic, exact-pinned. Python 3.10+. Fully typed (py.typed).

Install

pip install muse-code-sdk

You also need the Muse Code CLI: a muse binary on PATH, or an explicit path passed at spawn time.

Use

import asyncio

from muse_code import (
    MuseClient, MuseClientSpawnOptions, SendUserTurnOptions, StartSessionOptions,
)

async def main() -> None:
    client = await MuseClient.spawn(MuseClientSpawnOptions(
        muse_bin="muse",
        args=["serve"],
        client_info={"name": "my-app", "version": "1.0.0"},
    ))
    session = await client.start_session(StartSessionOptions(workspace_root="."))
    turn = await session.send_user_turn(SendUserTurnOptions(
        input=[{"type": "text", "text": "Summarize this repository."}],
        composer_input="Summarize this repository.",
    ))
    async for item in turn.items():
        print(item)
    await turn.completed
    await client.close()

asyncio.run(main())

To run a session and the child agents it starts without approval prompts, start it under the built-in :unrestricted permission profile. Current releases admit every child of such a session without prompts; a child admitted with a narrower authority would stay gated at it.

That profile is described, verbatim, as "No filesystem sandbox or approval prompts; local commands have direct network access; project trust is unchanged." It also sets the approval reviewer to none. Use it only for a trusted workspace and trusted prompts. Never use it where the prompts or the sandbox are what protects you.

Start it with that profile, and pass the same profile when you resume it. Paste inside main() above, indented, before await client.close(), with the same client:

from muse_code import ResumeSessionOptions, StartSessionOptions

session = await client.start_session(StartSessionOptions(
    workspace_root="/path/to/repo",  # an absolute path
    permission_profile=":unrestricted",
))
saved_session_id = session.session_id
# ... later, in the same client:
session = await client.resume_session(ResumeSessionOptions(
    session_id=saved_session_id,
    permission_profile=":unrestricted",
))

On start, require_permission_profile=True makes the client prove that the pick was applied, and raise PermissionProfileNotApplied if it cannot (a failed session/read read-back raises its own error). A host that does not report the committed selection fails that proof even when the pick was applied (seen with Muse Code 1.4.12). Resume has no require_permission_profile, so the client never verifies the pick there.

approval_mode alone is not enough: it changes the session's own approval mode, but its child agents are capped by the session's permission profile. Under a prompting profile (such as :ask-me, whose approval is on_request), the children still ask.

Documentation

Metadata

Release files for muse-code-sdk 1.4.14

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for muse-code-sdk 1.4.14
File Size Uploaded Provenance Actions
muse_code_sdk-1.4.14.tar.gz 273.8 kB With provenance Details for muse_code_sdk-1.4.14.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for muse-code-sdk 1.4.14
File Interpreter ABI Platform Actions
muse_code_sdk-1.4.14-py3-none-any.whl Python 3 none any Details for muse_code_sdk-1.4.14-py3-none-any.whl

Total release size: 401.9 kB

Release files / muse_code_sdk-1.4.14.tar.gz

Download URL muse_code_sdk-1.4.14.tar.gz
Size 273.8 kB
Tags Source
SHA-256 checksum
How to use checksums
2fec50924ade6e08918487568d978d3c332e1bbbbdb3030b705d84516c524820
BLAKE2b-256 checksum
How to use checksums
f562b20dd7357835f9294c06bc9b297a3f96f9f8e90f70f9340cd38e9ee978a0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

Release files / muse_code_sdk-1.4.14-py3-none-any.whl

Download URL muse_code_sdk-1.4.14-py3-none-any.whl
Size 128.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7eeacb4f822005724f4793deca2f31f8c403cdac05106a5ed4c05839e52369d7
BLAKE2b-256 checksum
How to use checksums
b5663ad21e0867176e207562499184fcad9a4d826c2849d4ec86b49762c7b526
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

Security for muse-code-sdk 1.4.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for muse_code_sdk-1.4.14.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page