Muse Code usage draining fast? Meta's fixes and resets

What Meta said about the Muse Code usage bug

"we are working to resolve a bug in how muse wonder and muse wonder full are counting against usage limits for Muse Code subscribers this is not intended behavior -- we will update everyone once we have fixed it and issue resets"

Alexandr Wang, Meta's chief AI officer, Oct 12, 2:34 PM ET (post 2109714291062620560)

"If you ran into usage issues earlier today, this has now been fixed. We've reset everyone's usage as compensation. Happy coding!"

Michael Douglas, Muse Code at Meta, Oct 12, 5:12 PM ET (post 2109754011452940542)

"we have identified and fixed the issue that was causing the unusually fast quota usage for muse wonder and muse wonder full. you will now see much lower usage against your limits. also, as promised, now that we've fixed the issue... muse code reset!!"

Alexandr Wang, Oct 12, 6:31 PM ET (post 2109774017574113780)

"Muse Code 1.4.8 is out and is focused on token efficiency. - Auto-review and background agents now use a cheaper model when available, and long auto-reviews stop sooner instead of burning tokens. - We've fixed a bug that routed a small number of users who had enabled contributor mode to the full-priced models."

Michael Douglas, Oct 14, 4:25 PM ET (post 2110466975474319865)

One heavy user, posting on Oct 12, said two Muse Wonder Full results on the $50 plan used "108% of the 5 hour limit and 36% of the weekly limit" (post). That is one report, not a Meta number, but it shows the scale people saw before the fix.

Why Muse Code can still drain fast after the fix

• Contributor mode is off. Meta says Contributor mode gives "more usage from your plan" in exchange for training on your content (Muse Code subscriptions). It is on by default, but it saves per computer, and headless muse exec runs can start with it off. Check with /settings.
• You're on Muse Wonder Full. It is the higher-capability variant on Power Usage and Maximum Usage. Meta doesn't publish how much faster it counts, but the Oct 12 bug and most complaints involved Wonder and Wonder Full.
• An old CLI. The 1.4.8 savings (cheaper model for auto-review and background agents, shorter auto-reviews) only apply if you've updated.
• Long sessions. /compact swaps history for a summary and /new starts fresh, so long threads stop resending everything.
• A stray API key. If META_API_KEY is set, Muse Code bills that key pay-as-you-go ahead of your plan. That isn't drain, but it can look like your plan isn't being used.

Out of Muse Code usage?

Meta gives two options: upgrade (type /upgrade, applies right away with a prorated charge) or wait for the limit to refresh. High Usage is $15, Power $50 and Maximum $200 a month (Meta, checked 2026-10-23). On Maximum, waiting is the only option. Muse Code usage limit reached covers each step.

Will Meta reset Muse Code again?

Meta hasn't promised another one. The latest was on Oct 15, 2:21 PM ET (post). Both October resets followed a fix, so a new bug fix is the likeliest trigger (our read). New resets land on the live resets page within the hour.