[BUG] Fable 5 session / 5-hour limit view disappears after reset while Fable bills via usage credits

[marlvinvu]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Confirmed: bar stays missing even during ACTIVE Fable usage

Fable 5 is currently in active use ([on claude.ai / in Claude Code]), and the
Fable 5-hour bar STILL does not appear:

• Claude Code /usage panel: only "5-hour limit", "Weekly · all models" and
  "Weekly · Fable" are shown.
• claude.ai → Settings → Usage: "Plan usage limits" shows only "Current session".

So this is NOT a case of the bar being hidden at 0% usage — it remains missing
while Fable is actively running. Weekly · Fable tracks correctly (31% used),
so Fable usage is still recorded at the weekly level; only the 5-hour/session
indicator for Fable is gone. It is also unclear whether current Fable usage is
now being silently counted into the generic 5-hour bar instead.

Timeline: hit 100% of the Fable 5-hour limit → overflowed into usage credits
($1.83 charged) → 5-hour window reset → the bar never came back.

Evidence: bar missing during ACTIVE Fable usage (before/after screenshots, ~10 min apart)

Two screenshots of claude.ai → Settings → Usage while actively using Fable 5:

	21:36	21:46
Current session	39% used	47% used
Weekly · All models	19% used	20% used
Weekly · Fable	31% used	32% used
Fable 5-hour bar	MISSING	STILL MISSING
Fable weekly reset	Mon 4:00 AM	Mon 3:59 AM

Observations:

• Weekly · Fable increased (31% → 32%), proving Fable usage is actively being
  recorded — yet no Fable-specific 5-hour/session bar appears anywhere.
• The generic "Current session" bar climbed 39% → 47% during the same period,
  consistent with Fable usage being counted only into the generic session
  bucket (there is no dedicated Fable bar for it to land in).
• The Fable weekly reset time also shifted from "Mon 4:00 AM" to "Mon 3:59 AM"
  between the two screenshots, suggesting the Fable limit window state was
  re-created or re-anchored at some point.

Timeline: hit 100% of the Fable 5-hour limit → overflow billed to usage
credits ($1.83) → 5-hour window reset → the Fable 5-hour bar never returned,
even during active Fable use. Same behavior in the Claude Code /usage panel
(desktop app) and on claude.ai.

What Should Happen?

After the 5-hour window resets, the Fable 5-hour bar should reappear (at 0% or current usage), the same way the generic 5-hour limit does.

Error Messages/Logs

Steps to Reproduce

1. Be on a Max (20x) plan with usage credits enabled (monthly spend limit set, e.g. $50).
2. Use Fable 5 until the Fable-specific 5-hour limit reaches 100%.
3. Continue using Fable 5 — the extra usage overflows and is billed to usage
   credits (in my case, $1.83 was charged).
4. Wait for the 5-hour window to reset.
5. Open the usage UI:
   • Claude Code (desktop app): run /usage
   • claude.ai: Settings → Usage
6. Observe: the Fable 5-hour bar is gone from BOTH surfaces — only the generic
   "5-hour limit" / "Current session" bar and the weekly bars ("Weekly · all
   models", "Weekly · Fable") remain.
7. Switch the model to Fable 5, keep using it, then refresh the usage UI.
8. The Fable 5-hour bar STILL does not appear, even though "Weekly · Fable"
   keeps increasing (31% → 32% within ~10 minutes), proving Fable usage is
   actively recorded. The generic "Current session" bar climbs instead
   (39% → 47%). The bar has never returned since the reset.

Claude Model

Other

Is this a regression?

I don't know

Last Working Version

2.1.206

Claude Code Version

2.1.206

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

This report is written by Fable 5.

[COOLak]

Adding related public billing / metering context because this should not be treated as only a missing UI bar.

The important accounting contradiction here is: Fable usage is still recorded in the weekly Fable bucket, the generic 5-hour/session meter moves during active Fable use, and overflow has already reached usage-credit billing, while the Fable-specific 5-hour meter never reappears after reset. That creates a customer-visible reconciliation gap: the user cannot see which bucket is enforcing, which bucket is debiting, or whether usage-credit overflow is being triggered by the intended Fable session-limit state.

Please route this to the Billing Platform / usage-ledger / entitlement owner in addition to the Claude Code UI/model owner. The review should reconcile:

• Fable 5-hour bucket lifecycle after reset
• weekly Fable bucket vs generic current-session bucket attribution
• usage-credit overflow trigger and debit attribution
• whether hidden or stale meter state can force paid overflow while the visible Fable meter is absent
• support-visible ledger state for the affected account
• credit/cap restoration policy if hidden meter state caused avoidable usage-credit billing

I am tracking this as related public context in a sanitized incident hub, without card data, payment IDs, support IDs, raw logs, screenshots, or private account details:
https://coolak.github.io/anthropic-claude-billing-incident/reconciliation-matrix.html