Five things happened in five weeks. Two were Muse releases; the other three were a sibling app, a model swap underneath and a subscription reshuffle and all three changed how Muse behaves anyway. That mismatch is why nobody can keep the timeline straight, so this page sorts each event by what it actually changed for you.
Only confirmed, dated releases are listed. A quiet stretch means nothing was announced not that nothing changed, which is a distinction this page takes seriously.
If that last-checked date is more than a few weeks old, treat this page as stale availability and limits are the two things most likely to have moved since.
Each one tagged by where it came from, and each one followed by the part that usually goes unsaid: what it changed for someone already using Muse.
Nine days after the iPhone release, the agent got its own Mac app working inside your apps rather than answering questions about them, with per-area access you grant and a confirmation prompt before anything sensitive. United States only at launch.
What it changed for you: everything, if you were waiting for it, and nothing if you were not in the US. It is a separate download from Meta AI, which trips up a lot of people expecting an update to an app they already had.
Every paid Meta tier moved under one subscription, rolled out globally, with standalone plans from around $2.99 a month up to business tiers at several hundred.
What it changed for you: nothing you had became paid. The practical effect was firmer rate limits on the free tier for compute-heavy features, which shows up as fewer tasks rather than a bill. Full breakdown.
The agent’s first appearance as its own product, nine days ahead of the Mac build.
What it changed for you: on a Mac, nothing directly but it is the reason the Mac app arrived as a version one rather than a beta of something older, and the reason the two share a task allowance rather than each having their own.
A one-million-token context window accepting text, images and video. Tool-use benchmarks improved Tau3-Bench Banking from 35% to 47%, Terminal-Bench 2.1 from 80% to 85% with roughly 20% fewer tool calls per task. Independent testing also found long-document accuracy slipped from 83% to 79%.
What it changed for you: results, without you doing anything. Brisker and more literal on multi-step work, slightly less reliable on long documents. This is the kind of change that never appears as a version number on your machine the numbers in full.
A native AppKit and SwiftUI app at 16 MB, Apple silicon and macOS 15 or later, distributed by Meta rather than through the Mac App Store.
What it changed for you: nothing about Muse but it is the single biggest source of confusion on this timeline, because it is a different app that reads a window rather than acting in it. The difference in full.
Two entries carry the Muse name; three did not, and changed it anyway. That ratio is the honest summary of this product’s first five weeks.
Changelogs invite you to read updates as a single stream of news. They are not. Five different kinds of thing get filed under “updates”, and they differ on the only question that matters to a user: will I find out?
Three of the five announce themselves. An app release asks you to install it. An availability change either hands you the product or does not. A permissions change puts a dialog in front of you.
The other two arrive quietly. A model swap and a tightened limit both change what you get back, without changing anything you can see.
That asymmetry is worth internalising, because the quiet two are also the ones most likely to break a habit you had built. A prompt you had refined over a fortnight can start behaving differently overnight, and nothing on your machine will have moved.
A new build with a version number, which you install when you choose to. Muse on the Mac and Meta AI for Mac are both this kind.
What to do: nothing urgent. Read what changed before installing if you depend on a specific behaviour. How updating works.
The engine is replaced server-side. Your app version does not move, your prompts are unchanged, and the answers are different. Spark 1.3 was this.
What to do: re-run one task you know well after any reported model change, and compare it against what you expected.
A country is added or a feature is switched on in a region. Binary, and for most of the world the only update that currently matters.
What to do: check rather than assume availability is account-based, not network-based. The eligibility gates.
The number of tasks a week, or what counts against them. Meta One tightened free-tier limits without changing any price you were paying.
What to do: notice when you start hitting a ceiling you did not used to hit. That is the symptom. How the meter works.
How an area of your Mac is accessed, or how a connected account is authorised. These put a dialog in front of you, which is the point of them.
What to do: read the dialog rather than dismissing it, and remember connections are revoked in the other service. Connections versus permissions.
Three kinds announce themselves and two do not. If you only build one habit from this page, make it the one attached to the model swap it is the change most likely to alter your results and least likely to tell you it happened.
Listed as open rather than dressed up as predictions. Meta has published no roadmap, so anything below with a date attached to it elsewhere is someone’s guess.
Meta has called the rollout expanding without naming a country or a date. This is the single change that would matter most to the most people, and there is nothing concrete to report. Availability.
Free-tier limits already tightened once, at the Meta One launch, without a price changing. Whether the current ceiling is the settled one or a starting position is not something Meta has addressed.
The granted areas today cover files, forms and the main native apps. Nothing has been said about what else might become reachable, and each addition would be a permissions decision as much as a feature.
The sandbox and the separation from advertising systems remain Meta’s account of Meta’s infrastructure. An independent audit would change that from a claim into a finding. None has been announced. What is claimed.
Because there is no published roadmap to report, and a changelog that mixes shipped features with anticipated ones stops being useful as a record. Everything dated on this page has already happened.
If you find a date attached to any of the four questions above, somewhere else on the internet, treat it as a guess until Meta says it.
Sources are Meta’s own announcements plus the published benchmark figures, attributed at the point of use. Where a number came from independent testing rather than Meta, the page says so.
Muse arriving on the Mac on 17 September 2026, nine days after the iPhone release. That is the most recent Muse release itself though the model underneath was replaced two weeks earlier and the subscription structure changed the day before. The timeline.
Not as of this page’s last check. Meta has described the rollout as expanding but has named no countries and no dates, so anything more specific than that is speculation. Availability.
Because the model underneath can be changed server-side without your app version moving at all. That is the most consequential kind of change and the one least visible to you, which is why a changelog alone will never tell you everything. The five kinds.
No. Nothing that was free became paid. What changed is that compute-heavy features got firmer rate limits on the free tier, so the practical effect is fewer tasks rather than a new bill. Meta One pricing.
Check the app’s own About panel. Knowing it is useful for reporting a problem, but it will not tell you which model version answered your last task, and those move independently.
No. It means nothing was announced and dated. Server-side changes routinely ship without notes, so a quiet stretch on any changelog is weaker evidence than it looks.
Availability, if you are outside the United States, because it decides whether you have the product at all. After that, model changes, because they alter results without altering anything you can see.
Ordinarily yes, but an update that changes how an area is accessed can require re-granting and connected accounts are separate from permissions, revoked in the other service’s settings. How that differs.
Not one Meta has published. Everything on this page is a dated event that has already happened; the open questions are listed as open rather than dressed up as forecasts.
It carries a last-checked date at the top of the status board. If that date is old, treat the page as stale and verify current availability and pricing with Meta directly.
An app release asks your permission. A model swap does not, and it is the one that will change what you get back tomorrow.
Independent guide not affiliated with Meta. Only confirmed, dated releases are listed; an absence of entries means nothing was announced rather than that nothing changed. Last checked 21 September 2026.