Loading today’s stories
Build2 distinct publishers3 min readPublished
Meta's terminal coding agent left beta on August 31 with plans from $5 to $50. That looks like a four-to-one discount on Codex and Claude Code seats, but line up the request bands and the gap narrows to two.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
The two published request bands overlap at the bottom, and that is where the budget lever gets complicated. Meta estimates roughly 10 to 50 requests every five hours on the $5 Everyday Usage plan [6]. OpenAI's pricing page estimates 10 to 100 local Codex messages every five hours on the $20 Plus plan running GPT-5.6 Sol [9]. If your work lands at the floor of both bands, you pay a quarter as much for the same ten units of work [1]. If it lands at the ceiling, Plus buys twice the messages for four times the money, so the per-message discount is 2x [2]. Both vendors say the count moves with model, task complexity, context, reasoning and tools [6][9]. The saving you actually get depends on your repository, not on the price page.
Extrapolating the ladder gets you 30 to 150 requests per five hours at $15 [5] and 100 to 500 at $50 [3], assuming Meta's stated 3x and 10x multiples apply to the request estimate rather than to some internal token budget [5]. Against OpenAI's $100 Pro 5x estimate of 50 to 500 [9], that is the same ceiling for half the price and twice the floor [3]. The Claude Code comparison cannot be run at all. Anthropic publishes no absolute prompt count for Pro, Max 5x or Max 20x, states the Max allowances as multiples of an unpublished base, and applies five-hour and weekly limits on top [10].
The pay-as-you-go rates make the trade explicit. Standard is $1.25 per million input tokens and $4.25 per million output; Contributor is $0.10 and $0.20 [11]. That is 12.5x cheaper on input and 21.25x cheaper on output [4], and the price of admission is opting in to Meta using your prompts and completions [12]. For the subscription saving to survive contact with real work, Muse Code's token consumption on your tasks has to stay inside whatever headroom the rate discount gives you, and that is measurable in an afternoon on one repository.
On mechanism, the coordination features are narrower than the word "workflow" suggests. Cross-session messaging lets separate jobs exchange messages while they run, and Meta has not claimed sessions share complete transcripts or working directories, so treat it as messaging rather than synchronization [14]. The durable part is older: a local append-only event log of model calls, tool runs, approvals and edits, which Meta says lets an interrupted session resume where it stopped [16]. The cookbook documents replaying sessions in CI and isolating subagents in separate Git worktrees [17], which is the kind of plumbing that decides whether parallel agents corrupt each other's checkouts. Workflows ship with a control room, but Meta has not published a cap on agent count, branching, retries or spending [15][20], so there is no way to know the size of a workflow before you run it.
Adoption cost is mostly patience. The plans arrive as a staged rollout [18] and the SDK is a developer preview [3], so a migration date is not yours to set yet.
Ranked by verification strength, evidence, and original report placement.
Meta took Muse Code out of beta on August 31st, adding cross-session messaging, workflows for coordinating teams of subagents, and monthly subscriptions starting at $5.
The release came 26 days after Meta introduced Muse Code as a beta product, and in a post on X Meta said the monthly plans were beginning to roll out on August 31st.
Meta put a Muse Code SDK into developer preview, giving developers an early route to build around the coding agent's runtime.
Muse Code runs in the terminal and uses Meta's Muse Spark 1.2 model to plan changes, edit code and validate its work across large repositories; Meta launched the model and agent together on August 5th.
Meta says the $5 plan typically provides around 10 to 50 requests every five hours, although the amount varies depending on the complexity of the work.
For the full launch Meta added inter-session messaging, Workflows that orchestrate teams of specialized agents with a dedicated Workflows control room, and a rewind feature that rolls conversation and code changes back to an earlier point in a session.
Distinct publishers with included, body-backed reporting in this cluster.
runtimewire.com
1 article · August 31, 2026
thenewstack.io
1 article · September 1, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
product
Meta budgeted up to $10bn a year with Anthropic even as Zuckerberg warns against rival AI labs1 distinct publisher
invest
Meta's coding agent has two prices: pay 18x more, or let it train on your repository1 distinct publisher
build
Developer habit, priced at $965B: what Anthropic's run actually proves1 distinct publisher
build
OpenAI puts latency on the price list: 750 tokens/sec, gated by workload fit3 distinct publishers
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
One announcement, one hands-on run
Strip out Meta's developer blog, its X posts and the rivals' pricing pages and almost nothing is left standing. The prices, the 10-to-50 request band, the resume-from-interruption behaviour and the 24-hour kernel runs are all the vendor describing itself, relayed accurately by two outlets. The one measurement anybody took is The New Stack's three-task run, which is first-hand but unreplicated and cuts against the sales pitch.
Day-one, no users counted
Everything observable here happened on the vendor's side of the transaction: a version out of beta, a price sheet, an SDK preview. No deployment, no seat count, no named team running Workflows in anger, and the plans themselves are still reaching accounts in stages. The closest thing to usage evidence is one reporter's three tasks.
The discount halves on inspection
A four-to-one price gap is the number everyone repeats, including a machine learning engineer calling the tiers refreshingly simple. Run the published bands and it is four-to-one only at the floor: at the ceiling, $5 buys 50 where $20 buys 100, which is two times cheaper per message. Then the one independent test finds the cheap agent burning substantially more tokens and shipping weaker work, so even the two-times figure flatters it on cost per finished job.
Cheap seats with data attached
Meta's cheapest token rates are 12.5 to 21 times below its own Standard prices in exchange for permission to train on prompts and completions — the discount is the product, and Msty AI's co-founder says as much when he calls the pricing unbelievably low and names Meta itself as the concern. Note also who is speaking: the outlet doing the price comparison is citing its own reporter's benchmark, and a rival tooling founder is quoted assessing a competitor's launch. Runtime Wire's account runs on a vendor blog post and vendor X posts.
Facts firm, meaning unsettled
On the checkable particulars the two accounts agree and neither contradicts the other, so dates, prices and feature names can be taken as reported. What is not settled is what the prices buy: request bands with complexity caveats on one side, undisclosed prompt counts on the other, and admitted gaps in what Meta has said about workflow scale and spending controls. Confident about the rate card, unconfident about the comparison it invites.