Repository navigation
Claude Max 20x is now Ultra, and verified Ultra accounts have no 5-hour limit #27750
Description
Problem
Anthropic renamed its Claude plans on 2026-10-30 (announcement, support article):
- Max 5x is now Max ($100/month)
- Max 20x is now Ultra ($200/month)
- Verified Ultra accounts no longer have a 5-hour limit. Newer Ultra accounts keep a temporary 5-hour limit until Anthropic verifies them. Weekly limits are unchanged, and Max still has the 5-hour window.
T3 Code is out of date in two places:
- Plan names.
claudeSubscriptionLabelinapps/server/src/provider/ClaudeProvider.tsstill returnsMax 5x/Max 20x. fix(server): Claude accounts show the new Max and Ultra plan names #27745 fixes this. - Docs. The FAQ entry "Why is my Claude 5-hour limit draining so fast?" (
docs/user/faq.md) assumes every Claude plan has a 5-hour limit.
Limits
Usage limits come from the data Claude reports, not from the plan. claudeUsageResponseToLimits (apps/server/src/provider/claudeUsageLimits.ts) skips a five_hour window that is null or has no utilization. A successful probe replaces all of the account's windows, so a verified Ultra account loses its Session row on the next probe, and the web, mobile, and widget views show only the weekly bars. The existing test in claudeUsageLimits.test.ts already covers a null utilization.
Still to check against a real verified Ultra account: whether the CLI still streams rate_limit_event with rateLimitType: "five_hour" mid-turn. If it does, that event would add a Session row back until the next probe.
Activity
ishaanko commentedon Oct 30, 2026
Checked a real Max 20x / Ultra account (
rateLimitTier: default_claude_max_20x) a few hours after the announcement. Anthropic's usage endpoint still reports an active 5-hour session window:So the T3 Code Session row matches what Anthropic reports for this account right now. Either the account isn't verified yet, or the endpoint hasn't caught up with the rollout. T3 Code should keep drawing whatever Claude reports rather than hiding the window by plan, because unverified Ultra accounts still have the limit.
Also relevant to #27745: the Agent SDK reports
subscriptionType: "max"for this Ultra account. The tier appears only inrateLimitTier, which the SDK doesn't expose, so a baremaxcan't be told apart from Ultra and will still be labeled "Max".ishaanko commentedon Oct 30, 2026
Closed #27751. Next step: once a verified Ultra account is available, check what
get_usagereturns forfive_hour(null, 0% with no reset time, or still counting) and fix only if T3 Code shows something Anthropic no longer enforces. Separately, #27745 still labels Ultra accounts "Max" because the SDK reportssubscription_type: "max"without the tier.