Skip to content

You've hit your limit · resets Feb 20, 5pm (Africa/Libreville) #25607

Closed as not planned

Description

@Brell241

Bug Description
Subject: Critical issue with weekly limits - service unusable despite active subscription
I'm experiencing a severe problem with Claude Code's weekly limits that makes the service completely unusable:
Timeline of the issue:

End of my previous subscription: Hit weekly limit, had to wait until February 13
February 13: Renewed my subscription, expecting limits to reset with new billing cycle
Today (February 13): Launched a task in Claude Code
Task blocked with message: "limit resets at 10pm today"
A few hours later: Limit reset time jumped from "10pm today" to "February 20, 5pm" - a full week away

The problem:

I already waited 7 days from my previous limit
I renewed my subscription expecting a fresh start
After launching ONE task today, I'm now blocked for another 7 days
The reset time changed inconsistently (22h → Feb 20)
The /usage display shows only "12% used" for the week, yet I'm completely blocked

Impact:
I've essentially been locked out for 14 days (Feb 6-13, now Feb 13-20) despite having an active paid subscription. This makes Claude Code completely unreliable for professional development work.
Request:

Immediate explanation of what caused this issue
Reset of my weekly limit or account credit for lost service time
Clarification on how subscription renewals should interact with weekly limits

I'm considering canceling my subscription as the service is currently unusable.

Environment Info

  • Platform: linux
  • Terminal: gnome-terminal
  • Version: 2.1.41
  • Feedback ID: 1b72432e-c911-4a36-aeb3-f093b13c1c0d

Errors

[{"error":"FileTooLargeError: File content (362.4KB) exceeds maximum allowed size (256KB). Please use offset and limit parameters to read specific portions of the file, or use the GrepTool to search for specific content.\n    at VwI (/$bunfs/root/claude:1136:402)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-13T17:01:10.924Z"},{"error":"MaxFileReadTokenExceededError: File content (71689 tokens) exceeds maximum allowed tokens (25000). Please use offset and limit parameters to read specific portions of the file, or use the GrepTool to search for specific content.\n    at jqI (/$bunfs/root/claude:1297:7592)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-13T17:01:11.447Z"},{"error":"MaxFileReadTokenExceededError: File content (43077 tokens) exceeds maximum allowed tokens (25000). Please use offset and limit parameters to read specific portions of the file, or use the GrepTool to search for specific content.\n    at jqI (/$bunfs/root/claude:1297:7592)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-13T17:01:16.049Z"},{"error":"FileTooLargeError: File content (362.4KB) exceeds maximum allowed size (256KB). Please use offset and limit parameters to read specific portions of the file, or use the GrepTool to search for specific content.\n    at VwI (/$bunfs/root/claude:1136:402)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-13T17:01:21.935Z"},{"error":"FileTooLargeError: File content (362.4KB) exceeds maximum allowed size (256KB). Please use offset and limit parameters to read specific portions of the file, or use the GrepTool to search for specific content.\n    at VwI (/$bunfs/root/claude:1136:402)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-13T17:01:22.077Z"},{"error":"FileTooLargeError: File content (362.4KB) exceeds maximum allowed size (256KB). Please use offset and limit parameters to read specific portions of the file, or use the GrepTool to search for specific content.\n    at VwI (/$bunfs/root/claude:1136:402)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-13T17:08:18.454Z"},{"error":"FileTooLargeError: File content (330.4KB) exceeds maximum allowed size (256KB). Please use offset and limit parameters to read specific portions of the file, or use the GrepTool to search for specific content.\n    at VwI (/$bunfs/root/claude:1136:402)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-13T17:08:24.645Z"},{"error":"MaxFileReadTokenExceededError: File content (71689 tokens) exceeds maximum allowed tokens (25000). Please use offset and limit parameters to read specific portions of the file, or use the GrepTool to search for specific content.\n    at jqI (/$bunfs/root/claude:1297:7592)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-13T17:08:25.447Z"},{"error":"MaxFileReadTokenExceededError: File content (99533 tokens) exceeds maximum allowed tokens (25000). Please use offset and limit parameters to read specific portions of the file, or use the GrepTool to search for specific content.\n    at jqI (/$bunfs/root/claude:1297:7592)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-02-13T17:08:26.085Z"},{"error":"MaxFileReadTokenExceededError: File content (99533 tokens) exceeds maximum allowed tokens (25000). Please use offset and limit parameters to read specific portions of the file, or use the GrepTool …

Note: Content was truncated.

Activity

  1. github-actions commented on Feb 13, 2026

    @github-actions

    Found 3 possible duplicate issues:

    1. [BUG] Weekly Limit Not Resetting on time #16618
    2. You've hit your limit · While usage is still at 84% #19673
    3. [BUG] Usage limit erreicht trotz verfügbarer Weekly Quota (85% verbraucht laut claude.ai) #22439

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  2. adamnickerson commented on Feb 13, 2026

    @adamnickerson

    I'm having this same issue.

    Description:

    Claude Code displays "You've hit your limit · resets Feb 20 at 12am (America/New_York)" when the actual usage dashboard
    shows significant remaining weekly capacity.

    Environment:

    • Claude Code (CLI) on macOS (Darwin 25.2.0)
    • Model: Claude Opus 4.6
    • Plan: Pro (with extra usage available)
    • Date of issue: Feb 13, 2026

    What happened:

    1. Claude Code displayed: You've hit your limit · resets Feb 20 at 12am (America/New_York)
    2. This reset date is exactly 7 days from the current date (Feb 13), implying the entire weekly budget was consumed
      instantly at the start of the cycle.
    3. Enabling "extra usage" allowed continued use.

    Dashboard at time of error (claude.ai/settings):

    • Current session: 100% used (resets in 1 hr 39 min)
    • Weekly - All models: 22% used (resets Fri 12:00 AM)
    • Weekly - Sonnet only: 57% used (resets Sun 5:59 PM)

    Expected behavior:
    The limit message should reflect the actual limit that was hit. Based on the dashboard, it appears to be a session rate
    limit (resets in ~1.5 hours), not a weekly limit resetting Feb 20.

    Actual behavior:
    Claude Code reports a reset date of Feb 20 (1 full week), which doesn't correspond to any limit shown on the usage
    dashboard. This is misleading — it suggests the user is locked out for a week when they may only need to wait ~2 hours.

  3. github-actions commented on Mar 14, 2026

    @github-actions

    Closing for now — inactive for too long. Please open a new issue if this is still relevant.

  4. github-actions commented on Mar 23, 2026

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  5. locked as resolved and limited conversation to collaborators on Mar 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingplatform:linuxIssue specifically occurs on LinuxstaleIssue is inactive

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions