[BUG] /usage no longer renders the per-model weekly bar (Weekly · Fable) — weekly_scoped limit present in payload but dropped (scope.model.id is null)

Status Open
Reported on v2.1.212
Maintainer reply None cached
Activity 1 comment · opened Jul 17, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet (closest relatives: #76427, #73451, #74096 — all describe different manifestations; details below)
  • [x] This is a single bug report
  • [x] I am using the latest version of Claude Code (2.1.212)

What's Wrong?

Until ~Jul 16 2026, /usage showed a model-scoped weekly bar for Fable ("Weekly · Fable") alongside the session and all-models bars. Since then the per-model bar no longer renders — /usage shows only:

  • Current session (e.g. 51% used)
  • Current week (all models) (e.g. 42% used)

The data is still being delivered. The cachedUsageUtilization blob in ~/.claude.json, fetched minutes before running /usage, contains a third limit that the TUI does not render:

{
  "kind": "weekly_scoped",
  "group": "weekly",
  "percent": 44,
  "severity": "normal",
  "resets_at": "2026-07-17T22:59:59.679456+00:00",
  "scope": {
    "model": {
      "id": null,
      "display_name": "Fable"
    },
    "surface": null
  },
  "is_active": false
}

Note scope.model.id is null (only display_name is set). If the renderer keys the per-model bar off the model id, a null id would silently drop it. This may be a server-side payload change on this account rather than a pure client bug.

Environment

  • Claude Code 2.1.212 (native install), macOS (darwin 25.5.0)
  • Claude Max 20x subscription (organizationRateLimitTier: "default_claude_max_20x")
  • Timeline: per-model bar last seen Jul 15/16; auto-updates installed 2.1.211 on Jul 15 20:12 local and 2.1.212 on Jul 16 21:28 local

What I ruled out

  1. Not a 2.1.212 client regression. Running the previous binary (~/.local/share/claude/versions/2.1.211) against the same account state renders the identical output — no Fable bar there either. The bar also disappeared during Jul 16 daytime, while still on 2.1.211.
  2. Not stale auth/profile. Full logout + re-login did not change anything.
  3. Not the local subscription flags. ~/.claude.json had a genuine misdetection — claudeMaxTier: "not_max", hasAvailableMaxSubscription: false, recommendedSubscription: "pro" — contradicting the fetched profile on the same file (organizationType: "claude_max", organizationRateLimitTier: "default_claude_max_20x"). Manually correcting these flags (with all sessions closed) persisted but did not restore the bar. Filing this contradiction as a secondary finding since re-login never recomputed the derived flags.
  4. Not account-wide. The Claude desktop app (Settings → Usage) shows Fable weekly usage correctly for this same account.
  5. Not plan-wide. A colleague on the same Max plan still sees the per-model Fable bar in /usage on their machine.

Possibly related

  • #76427 — inverse manifestation: Fable 5-hour bar disappeared (after Fable usage overflowed into usage credits) while the weekly Fable bar kept rendering. On this account, the payload's extra_usage block reports is_enabled: false with disabled_reason: "out_of_credits", so a billing/credit state transition flipping a server-side display field may be a shared mechanism.
  • #73451 — /usage missing Fable session metrics (v2.1.198, pre-dates this).
  • #74096 — quick-view popup omits Fable usage (desktop UI feature request).
  • #77453 / #78232 — feature requests to expose the per-model weekly buckets in statusline JSON; both describe the per-model data as rendering in /usage as of mid-July, consistent with this being a recent break.

Expected

/usage renders the "Weekly · Fable" bar whenever the payload contains a weekly_scoped limit — or, if the payload is considered malformed (scope.model.id: null), fails loudly rather than silently dropping the user's most relevant limit. Meanwhile the only way to see Fable standing from the CLI is to read cachedUsageUtilization out of ~/.claude.json by hand.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗