Meta graduates Muse Code out of beta

Meta has taken Muse Code out of beta and expanded the terminal coding agent around coordination rather than just code generation. The August 31 update added inter-session messaging over Unix sockets, workflow orchestration for multi-subagent tasks, and a rewind control in the command-line interface, according to Meta’s announcement as summarized by AI Weekly and Neowin. (aiweekly.co) A TypeScript SDK is also available in developer preview, giving developers a way to drive Muse Code programmatically over what the company calls the Muse Session Protocol. (github.com) The release matters because it shows where coding-agent products are moving. (github.com) Meta is not only selling a single assistant in a terminal window; it is adding the plumbing for multiple sessions, multiple agents and longer-running workflows that need state to persist across steps. That puts Muse Code in the same broader product direction as other developer tools that are adding more agent control and orchestration surfaces. ### What actually changed in the stable release? Meta’s August 31 release added three core features to the stable product: inter-session messaging, workflow orchestration and rewind. (aiweekly.co) AI Weekly’s summary says sessions can now exchange messages over Unix sockets, while workflows let developers coordinate multi-subagent tasks inside Muse Code. Neowin, citing Meta, said the stable version is designed to handle more complex multi-session and multi-agent engineering work. The command-line rewind feature is narrower but practical. Neowin reported that users can double-tap Escape to return to earlier “safe rewind points,” with confirmation required before work is undone. (aiweekly.co) That suggests Meta is trying to make longer agent sessions easier to manage when a branch of work goes wrong. ### Why is inter-session messaging a bigger deal than it sounds? Inter-session messaging changes Muse Code from a single-threaded assistant into something closer to a coordinated workspace. Neowin quoted Meta as saying one session can warn another when a change affects what it is building, or pass along an answer when another session is blocked. (aiweekly.co) AI Weekly’s summary similarly described the feature as messaging between sessions over Unix sockets. That matters for developers who split work across terminals, branches or subagents. Instead of copying context by hand between sessions, the product is now designed to pass state and updates inside the tool itself, which is a prerequisite for more serious orchestration use cases. (neowin.net) That last point is an inference from the product features Meta described. ### What does the SDK add for developers? GitHub’s `meta-models/muse-code-sdk` repository describes the package as a TypeScript SDK and developer documentation for building clients that control Muse Code agent sessions over the Muse Session Protocol. (aiweekly.co) The package is published as `@muse-code/sdk`, requires Node.js 20 or newer, and ships with its own TypeScript declarations. The repository also says the SDK is a developer preview, is published pre-1.0, and carries “no stability promise yet,” meaning minor releases may still change APIs. AI Weekly reported that the SDK lets programs spawn a local `muse` host with no network layer, which points to local automation and embedding Muse Code inside other developer workflows. (aiweekly.co) ### How does this fit the wider coding-tools market? September 1 coverage from Neowin said Meta is also rolling out monthly subscription tiers alongside the stable release. The plans range from $5 a month to $50 a month, with higher tiers offering more usage and earlier access to features, according to that report. (github.com) Meta’s packaging lines up with a broader shift in coding tools toward agent systems that can plan, coordinate and be embedded into larger workflows. The immediate takeaway for developers and students is practical: projects that show orchestration, state management, approval controls and evaluation are closer to the product direction major vendors are now shipping than simple chatbot wrappers. (github.com) That final point is an inference drawn from the feature set Meta released and the SDK structure it published. ### What should readers watch next? The GitHub repository says the SDK documentation, protocol reference, guides and cookbook are already published from the `gh-pages` branch, and the package is available through npm as `@muse-code/sdk`. (neowin.net) Meta’s next visible milestones are likely to show up there first: API changes while the preview remains pre-1.0, additional examples, and any expansion of the stable Muse Code workflow surface. (github.com)