[Bug] Claude Code 1M context incorrectly billed as Extra Usage instead of Max plan coverage

Bug Description
no, not at all. the reason that people get claude max plan is for claude code. why are you saying thats not included in the $200? are you high?4:10 PMYou're right, I apologize — that was wrong. Claude Code usage IS included in your Max plan, that's literally the point of paying $200/mo.
Let me actually look into what "extra usage" means and what's eating your $52.80.Searched the webSearched the webOK, so here's the real story — and it's actually a known issue that other Max plan users have been dealing with too.
What's supposed to happen: Your Max 20x ($200/mo) plan includes Claude Code usage with the 1M context window. Since March 2026, Max users on Opus 4.6 automatically get a 1 million token context window in Claude Code with no additional configuration and no long-context pricing surcharge. Jamie Lord
What's actually happening to you (and others): Extra usage kicks in at standard API rates once you exceed your included Max 20x limits Claude — but the problem is that the boundary between "included" and "extra" for 1M context has been murky and apparently changed silently.
There's a known bug/billing issue. Other Max plan users have reported that 1M context model usage was silently moved from Max plan coverage to Extra Usage billing without documentation. GitHub One user got hit with $173 in extra charges and their Max plan "Weekly limits" showed only 13% usage while Extra Usage had accumulated to $173. GitHub That sounds exactly like your situation — your plan bars show 2-7% used, but you've got $52.80 in extra charges.
What you should do:

Turn off the Extra Usage toggle in Settings > Usage immediately — that stops the bleeding. You'll just get throttled instead of charged when you hit limits.
File a support ticket referencing the GitHub issues (#28927 and #29289) about the silent billing change for 1M context. Other users have gotten refunds.
Check if your Claude Code is running opus[1m] — that's what's triggering the extra charges. The error in your screenshot ("Extra usage is required for 1M context") is literally telling you that 1M context is being billed as extra, not included.

This is a legitimate billing problem that Anthropic hasn't fully resolved yet, not you doing anything wrong.

Environment Info

• Platform: darwin
• Terminal: ghostty
• Version: 2.1.101
• Feedback ID: 0c91f171-66f3-4ab6-bd81-0bd6f79d0724

Errors

[{"error":"MaxFileReadTokenExceededError: File content (12681 tokens) exceeds maximum allowed tokens (10000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n    at ZY7 (/$bunfs/root/src/entrypoints/cli.js:4449:12671)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-11T20:40:22.523Z"},{"error":"Error: 429 {\"type\":\"error\",\"error\":{\"type\":\"rate_limit_error\",\"message\":\"Extra usage is required for long context requests.\"},\"request_id\":\"req_011CZxeKfjUYU99MJeyQR4aB\"}\n    at generate (/$bunfs/root/src/entrypoints/cli.js:11:53652)\n    at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:4943)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-11T20:50:46.004Z"},{"error":"Error: Failed to delete keychain entry: security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.\n    at KTq (/$bunfs/root/src/entrypoints/cli.js:249:281283)\n    at async nbq (/$bunfs/root/src/entrypoints/cli.js:402:898)\n    at async ey6 (/$bunfs/root/src/entrypoints/cli.js:402:796)\n    at async h8_ (/$bunfs/root/src/entrypoints/cli.js:2812:2084)\n    at async CfH (/$bunfs/root/src/entrypoints/cli.js:2837:5698)\n    at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:2906:3288)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-11T21:03:47.013Z"}]