Superpower Daily
OpenAI Reportedly Tests Pay-on-Completion AI Deals With Some La...Broadcom Releases AgentMinder to Check AI Agent Tool Calls at R...AWS Agent Registry Reaches GA With Approval Gates for Enterpris...Vanta Releases 65 Agent Controls, Drawing a Line Between Govern...Microsoft Releases GigaPath-Flash, Reporting Roughly 50x Less C...Claims Adjusters’ AI Backlash Hits 98% Negative Reviews as Insu...OpenAI Reportedly Tests Pay-on-Completion AI Deals With Some La...Broadcom Releases AgentMinder to Check AI Agent Tool Calls at R...AWS Agent Registry Reaches GA With Approval Gates for Enterpris...Vanta Releases 65 Agent Controls, Drawing a Line Between Govern...Microsoft Releases GigaPath-Flash, Reporting Roughly 50x Less C...Claims Adjusters’ AI Backlash Hits 98% Negative Reviews as Insu...
Toolspublished

Muse Code Exits Beta With Agent SDK Preview and Monthly Plans

The coding tool now offers a preview route for developers to build agents on top of it, while pricing and access mechanics remain unannounced.

By 2 min read
Muse Code Exits Beta With Agent SDK Preview and Monthly Plans
Muse Code Exits Beta With Agent SDK Preview and Monthly Plans
Sign in to save and react

Listen to this story

The audio brief

About 1:14
0:001:14
Read transcript
Muse Code has exited beta with two important additions: a developer-preview SDK for building agents on top of the coding tool, and monthly subscription plans that are now rolling out. That gives developers a stated way to extend Muse Code, while giving users a recurring paid route into the product. But the commercial and technical terms are still largely undefined. There are no disclosed prices or usage limits, and the SDK release does not yet specify its interfaces, who can access the preview, or when a broader release might arrive. For developers who want something concrete to try, the clearest artifact is a shell installer for the muse command-line tool. It requires curl and mktemp, downloads the launcher from an API endpoint, and normally places it in the user’s local bin directory. The installer follows up to three HTTPS redirects, checks the downloaded file’s Bash syntax, and compares it against a SHA-256 digest when the server provides a valid checksum. Older servers may not provide one. The script also attempts to add its installation directory to the user’s PATH, unless that behavior is disabled through an environment variable. So the beta exit is real, but the most consequential details remain open: how much the plans cost, how the SDK works, and how widely developers can use it.

Story brief

3 key points

Muse Code is moving from beta into a paid, extensible phase, pairing a developer-preview SDK for building agents with monthly subscriptions. The SDK’s commercial and technical details remain unspecified: there is no pricing, usage limits, interface documentation, access policy, or target date for general availability. For hands-on users, the clearest immediate artifact is a shell installer for the `muse` CLI, with...

  1. 01

    The SDK is explicitly for building agents on top of Muse Code, but remains in developer preview.

  2. 02

    Monthly plans are rolling out without disclosed prices or usage limits.

  3. 03

    The installer supports up to three HTTPS redirects and validates SHA-256 when the server supplies a checksum.

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.

Sources

  1. dev.meta.ai1/ muse code is out of beta. launching with an sdk in developer preview to build your own agents on top of it and rolling out monthly subscription plans. copy-paste into your termi

Related coverage

Continue reading