Muse Code quota disappears while the 5-hour window is idle

[enieuwy]

Summary

Muse Code usage disappears from CodexBar whenever the 5-hour window is idle, even when the weekly limit has real usage.

POST https://api.meta.ai/muse-code/key (the endpoint both the Muse CLI and the bundled muse plugin read) omits subs_usage entirely while the 5-hour window is idle. The Muse CLI's own /usage then shows "Currently unavailable", and CodexBar shows Quota: Not included in this login response with no bars — so the weekly limit is invisible between sessions.

Evidence (one Muse Code Everyday Usage account, CodexBar 0.66.0, Muse Code 1.4.0-R4161.1)

Time (AWST)	/muse-code/key	dev.meta.ai usage page
2026-09-25 15:32	no subs_usage	5 hours 0%, weekly 0%
2026-09-25 21:22	no subs_usage	5 hours idle, weekly 15%
2026-09-25 22:45 (after using Muse)	subs_usage present: 6% / 17%	matches
2026-09-26 03:22	no subs_usage	5 hours idle, weekly 22.6%

The response is otherwise healthy: HTTP 200, is_subs_active: true, plan name present. So this is Meta's response shape, not a login or Keychain failure.

The dev.meta.ai/usage page gets the same subscription quota from plain JSON GET endpoints authenticated by the llama_dev_sess browser cookie:

• GET /api/portal/teams
• GET /api/portal/teams/{team_id}/subscription-quota → window_weighted_used/limit, weekly_weighted_used/limit, weekly_resets_at, and window_resets_at only while the 5-hour window is active.

No form-encoded GraphQL, CSRF tokens, or build-specific Server Action IDs are involved, so it fits the bundled plugin host's browser-cookies + JSON HTTP capabilities.

Existing coverage searched

• [codex] Add Muse browser usage, spend, and token display #2936 (closed): dev.meta.ai developer-team spend via form-encoded GraphQL / WebKit — different data, outside the plugin boundary.
• Add Muse desktop usage provider #3864 (closed): Muse desktop app via Accessibility — outside the plugin boundary.
• fix(muse): recover Keychain-disabled and windowless mint responses #3772 (closed; adopted by the maintainer): label for windowless mint responses — keeps plan identity but cannot show the quota.
• Support Muse (muse.ai) Power / Maximum personal agent subscriptions, distinct from Muse Code CLI #3797 (open): muse.ai Power / Maximum personal-agent plans — different product.
• Support Meta Muse Code (Muse Spark) #3409 (closed): original Muse Code request.

Also reported to Meta via the Muse CLI /feedback.

[clawsweeper]

Codex review: this still needs some work. Reviewed September 25, 2026, 3:53 PM ET / 19:53 UTC.

Summary
Current main and v0.66.0 still leave the weekly quota blank when Meta omits subs_usage. The linked open PR explicitly addresses that behavior, so this issue should remain open while that candidate is reviewed.

Reproducibility: yes. for the display path: an active response without subs_usage deterministically produces no quota bars in current source and its fixture. The reporter’s claim about when Meta omits the field was not independently exercised here.

Maintainer decision needed

Question	Recommendation
Should Muse Code offer opt-in browser-session access to recover subscription quotas omitted by the CLI login endpoint?	Approve a scoped fallback: Review the linked PR for explicit opt-in, account matching, credential scoping, and soft failure before accepting browser quota data.

Why: The proposed data source would access browser credentials, which VISION.md places behind authentication and privacy sign-off.

Next step
The linked open PR owns the proposed implementation; review it and obtain the required browser-session policy decision before resolving this issue.

Review details

Best possible solution:

Keep the device-token response primary and, if approved, use an opt-in, same-account browser-session fallback only when it omits quota data; retain the current soft failure when web data is unavailable.

Do we have a high-confidence way to reproduce the issue?

Yes for the display path: an active response without subs_usage deterministically produces no quota bars in current source and its fixture. The reporter’s claim about when Meta omits the field was not independently exercised here.

Is this the best way to solve the issue?

Unclear until maintainer sign-off. The linked PR’s opt-in fallback fits the existing plugin boundary, but browser credential use and account matching need review.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• Using a browser session for quota data changes the Muse provider’s authentication and privacy boundary; the opt-in and same-account behavior need maintainer sign-off.

Codex review notes: model internal, reasoning medium; reviewed against a2cf7face10b.

Label changes

Label changes:

• add P2: Muse Code subscribers lose quota visibility between sessions, with impact limited to this provider’s usage display.
• add impact:ux-friction: The weekly quota remains available on Meta’s usage page but disappears from CodexBar during the reported idle window.
• add issue-rating: 🦞 diamond lobster: Current issue advisory state selects this label.
• add clawsweeper:source-repro: Current issue advisory state selects this label.
• add clawsweeper:linked-pr-open: Current issue advisory state selects this label.
• add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
• add clawsweeper:needs-product-decision: Current issue advisory state selects this label.

Label justifications:

• P2: Muse Code subscribers lose quota visibility between sessions, with impact limited to this provider’s usage display.
• impact:ux-friction: The weekly quota remains available on Meta’s usage page but disappears from CodexBar during the reported idle window.

Evidence reviewed

What I checked:

• Current quota path: The plugin returns the plan and an unavailable-quota note immediately when subs_usage is absent, before creating either quota window. (Sources/CodexBarCore/Resources/Plugins/muse.ts:71, a2cf7face10b)
• Expected current behavior: A focused fixture asserts that an active login without quota windows has no primary or secondary quota, while retaining plan identity. (Tests/CodexBarTests/MusePluginTests.swift:103, a2cf7face10b)
• Documented limitation: The Muse documentation explicitly describes the no-bars result for an active subscription whose mint response omits subs_usage. (docs/muse.md:42, a2cf7face10b)
• Release check: The v0.66.0 plugin has the same early return for omitted subs_usage; the reported behavior is therefore present in the latest listed release. (Sources/CodexBarCore/Resources/Plugins/muse.ts:71, e665cbf64976)
• Feature history: The Muse plugin history records the subscription-quota implementation and a later change preserving identity when the response has no windows. Older parent blobs were unavailable locally, so this does not assert exact line introduction. (Sources/CodexBarCore/Resources/Plugins/muse.ts:71, 5f21b84c7f2f)
• Linked implementation candidate: The provided GitHub context identifies open PR Muse Code: read omitted quotas from dev.meta.ai with an opt-in browser session #4003 as a closing-reference candidate. Its body proposes an opt-in same-account browser-session fallback and reports a real-account CLI comparison; those claims still need PR review. (6f2a24cd52b7)

Likely related people:

• Peter Steinberger: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
• 唐鳳: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[steipete]

Thanks @enieuwy for the API trace. Current main reproduces the no-bars result when an active login omits subs_usage. The omitted block includes weekly usage, so treating it as a full allowance would hide real usage rather than recover it. The browser endpoint can supply the missing data, but we still need to establish which web team/subscription belongs to the CLI login. Keeping this issue open; no mapper-only fix is claimed.

[steipete]

Fixed on main via #4011 and shipping in 0.67.1. When Meta's API omits the quota block for an idle window, CodexBar can now read the quota for a team you explicitly select from dev.meta.ai through an opt-in, domain-scoped browser session; the row is labeled as that team's browser quota rather than as the CLI plan, and nothing is invented when no team is selected. Thanks @enieuwy!