You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Show Muse Code (Meta) accounts from a CLIProxyAPI hub in Usage → Limits
#25566
When Muse Code runs through a CLIProxyAPI hub, Usage → Limits should show each pooled Meta account's session (5-hour) and weekly windows, the way it already shows pooled Codex and Claude accounts.
Meta only sends the windows inside the response stream (response.subscription_usage), and CLIProxyAPI currently discards that event. For Codex and Claude the hub calls a usage endpoint through api-call; I couldn't find one for Meta.
Here: once that exists, cliproxyApi.ts includes Meta accounts and maps window and weekly (used_percent, resets_at, window_duration_mins) to Session and Weekly windows, labelled Muse Code. Each reading is a snapshot from the last response, so it should show an "as of" time like the direct-Muse windows in fix(server): Muse Code's subscription usage shows in Usage → Limits #25165.
I'm happy to test against a real hub with Meta subscription accounts, or to open the PR once the upstream API exists.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
What I'd like
When Muse Code runs through a CLIProxyAPI hub, Usage → Limits should show each pooled Meta account's session (5-hour) and weekly windows, the way it already shows pooled Codex and Claude accounts.
Why it doesn't work today
apps/server/src/usage/cliproxyApi.ts#L367.usage/changednotification, which only works when Muse signs in to Meta directly. Pointed at a proxy, Muse authenticates with an API key and reports no allowance (muse usage --json→{"allowance":null,"reason":"api_key"}), so that PR doesn't cover this setup.response.subscription_usage), and CLIProxyAPI currently discards that event. For Codex and Claude the hub calls a usage endpoint throughapi-call; I couldn't find one for Meta.What it needs
response.subscription_usageand exposes it through the management API: Meta (Muse Code): store each account's subscription usage and expose it through the management API router-for-me/CLIProxyAPI#7018.cliproxyApi.tsincludes Meta accounts and mapswindowandweekly(used_percent,resets_at,window_duration_mins) to Session and Weekly windows, labelled Muse Code. Each reading is a snapshot from the last response, so it should show an "as of" time like the direct-Muse windows in fix(server): Muse Code's subscription usage shows in Usage → Limits #25165.I'm happy to test against a real hub with Meta subscription accounts, or to open the PR once the upstream API exists.
All reactions