[BUG] Sudden 30+ hour lockout from using Claude Code and Claude.ai during critical bulld 3 days before beta launch

Resolved 💬 3 comments Opened Apr 17, 2026 by dintlnomad-web Closed Apr 20, 2026

Preflight Checklist

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

What's Wrong?

30-hour lockout during a critical build window with no warning after 80% of used warning, no degraded-service fallback, and no visibility into remaining budget. even if the rate limit itself is working as designed. The bug is: no warning before cutoff + no way to check remaining budget from the CLI.

What Should Happen?

Warn me when am 5% away from lockdown. Create a way for me to check my usage in the CLI.

Error Messages/Logs

Error editing file
  ⎿  You've hit your limit · resets Apr 15 at 10pm (America/Chicago)
     /extra-usage to finish what you’re working on.

Steps to Reproduce

  1. Use Claude Code
  2. Get blocked from using Claude Code ad Claude.ai
  3. Wait 30+ hours to resume build

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Opus 4.6

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗