Product1 publisher2 min readPublished
Meta's Muse Code subscription rations prompts in five-hour windows
The entry plan allows 10 to 50 prompts every five hours, and the page does not say what puts a subscriber at either end of that band. Running out mid-session points the developer at a prorated upgrade.
The Product Desk · Product desk
What happened
- Meta's Muse Code documentation sells the coding agent as a flat monthly rate in place of per-token billing, across three plans named Everyday Usage, High Usage and Power Usage.
- The Everyday Usage plan allows 10 to 50 prompts every five hours, including image and video uploads, and adds voice mode and web search.
- High Usage is described as 5x more usage than the entry plan and Power Usage as 20x, with higher file uploads and early access to new features.
- A subscriber who reaches a plan's usage limit can either upgrade to the next plan or wait until the limit refreshes.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- constraint A buyer cannot forecast capacity per developer before checkout, because the entry allowance varies fivefold and the region-specific benefits only appear during onboarding.
- decision Teams running the agent in CI or scripts have to fund that work as a separate per-token line, because the subscription credential only answers inside the CLI.
- cost A single busy week raises the monthly rate past the end of that week, because the upgrade bills prorated the same day and the downgrade waits for the next cycle.
- exposure Whoever signs this off has to ask the question for every model, since Meta says its use of inputs and outputs, including submitted code, depends on which models the developer selects.
The rationing is visible from the prompt line. Typing `/upgrade` in an interactive session opens Accounts Center in a browser [14]. An upgrade takes effect immediately, with a prorated charge for the rest of the billing cycle [12]. A downgrade waits for the start of the next cycle, and the subscriber keeps the current limit until then [13].
Count what the entry tier actually buys. Five-hour windows do not line up with a working day: on the plan's stated band, eight hours spans 1.6 windows, which puts the floor at about 16 prompts a day and the ceiling at about 80 [1]. Meta does not disclose what puts a given subscriber at 10 or at 50, and it says benefits and availability may vary by region, with the available benefits shown during onboarding before you subscribe [15].
The two higher tiers are sold as multiples, not counts: High Usage is 5x more usage than Everyday, Power Usage 20x [5][6]. Applied to the entry allowance, that works out to 50 to 250 prompts per five hours on High Usage and 200 to 1,000 on Power Usage [3]. The spread inside the entry plan is itself fivefold, the same step the page sells between Everyday and High Usage [2]. Meta lists no prices on the subscriptions page [20].
The flat rate only covers a person at a keyboard. It works through the Muse Code CLI while signed in with a Meta Model API account [9], attached to the API key that CLI onboarding connects automatically, a credential usable with Muse Code only [10]. Anything that runs unattended needs a second budget line at per-token rates [11]. The page also says a subscription ends one of two ways: the subscriber cancels, or Meta revokes it [16].
Most teams do not have the figure this decision needs. What matters is the count in each developer's busiest five-hour block, measured over two weeks of real work, because a cap bites on the worst Thursday afternoon. Two things then sort the plan: whether a person is at the keyboard, and whether demand is steady or bursty. Steady interactive work fits a flat monthly rate with a five-hour window. Bursty interactive work means buying the top tier and leaving most of it idle, and on Power Usage the only listed remedy for a spent limit is waiting for it to refresh [8].
What to watch
- Whether Meta replaces the 5x and 20x multipliers with stated prompt counts for High and Power Usage.
- Whether the subscription credential is ever allowed to work outside the Muse Code CLI, for headless or CI use.
- Which benefits Meta actually shows at onboarding in which regions, since the page says availability varies.