Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] 5-hour session quota is misleading — actual limit is token-based, not time-based

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

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?

The session is labeled as a 5-hour quota, but in practice the limit is hit based on token/context usage, not elapsed time. On a project with a moderate-sized codebase, system prompts, and memory files, the limit can be reached in under an hour with only a handful of prompts.

The "5hr" label sets a false expectation. Users should be clearly informed that the quota is token-based, and the UI should reflect remaining context, not time.

What Should Happen?

Expected: Session lasts up to 5 hours as advertised Actual: Session context exhausted in under 1 hour

Error Messages/Logs

Steps to Reproduce

Steps to reproduce:

Open Claude Code on a project with CLAUDE.md, memory files, and a multi-package monorepo Run 3–5 prompts that involve file reads Observe context percentage climbing rapidly — well under 1 hour

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

N/A using plugin in VSCode

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

Update the UI to reflect the token-based quota instead of time-based to accurately inform users about the session limit.

Guidance

  • Review the current implementation of the session quota and identify where the time-based label is being displayed to users.
  • Modify the UI to display the remaining context instead of time to provide a more accurate representation of the session limit.
  • Consider adding a tooltip or documentation to explain that the quota is based on token/context usage, not elapsed time, to set clear expectations for users.
  • Test the updated UI with different project sizes and prompt scenarios to ensure the displayed context limit accurately reflects the actual session duration.

Example

No code snippet is provided as the issue does not contain specific code references.

Notes

The solution assumes that the development team has access to modify the UI and has a clear understanding of how the token-based quota is calculated. Additional investigation may be required to determine the exact implementation details.

Recommendation

Apply workaround: Update the UI to reflect the token-based quota to provide accurate information to users, as the root cause of the issue is the misleading time-based label.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] 5-hour session quota is misleading — actual limit is token-based, not time-based