Muse Code Exits Beta With Agent SDK Preview and Monthly Plans

Muse Code has left beta with two new tracks: a developer-preview SDK for building agents on top of the coding tool, and monthly subscription plans now rolling out. The change gives developers a stated path to extend the product while introducing a recurring paid offering.

A beta exit with two new routes

The technical route is a developer-preview SDK for building agents on Muse Code. The commercial route is a subscription rollout. Together, they move the product beyond beta, but the release does not give terms for the preview or paid plans.

The platform layer is still a preview

An SDK is the product layer that lets outside developers program against a tool rather than use only its built-in interface. Here, the stated purpose is agent creation on top of Muse Code. Developer preview status signals that this is an early access stage, rather than a broadly described finished interface.

The tangible release path remains command-line based

The published material also includes a shell-based installer for the muse command-line tool. By default, it places the launcher in the user’s local bin directory and downloads it from an API endpoint, unless installation-directory or launcher-URL environment variables are set.

The installer needs curl and mktemp, allows up to three HTTPS redirects, and checks the downloaded launcher’s Bash syntax. If the server provides a valid checksum header, it compares the file with a SHA-256 digest. The script says older servers may not provide one. It also tries to add its install directory to the user’s PATH unless an environment variable turns that off.

The next terms are still open

The launch confirms the subscription rollout and SDK preview, but gives no pricing, usage limits, SDK interfaces, preview access rules, or broader-release date. Those details will shape how easily teams can use the agent-building tools in their development work.