claude-code - 💡(How to fix) Fix [Bug] Budget tracking shows weekly usage instead of session when session budget selected [1 participants]

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…
GitHub stats
anthropics/claude-code#45281Fetched 2026-04-09 08:09:01
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
labeled ×4

Error Message

[{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3447)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-08T14:46:01.743Z"},{"error":"MaxFileReadTokenExceededError: File content (46461 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 CT7 (/$bunfs/root/src/entrypoints/cli.js:4309:13191)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-08T14:59:43.174Z"}]

Code Example

[{"error":"Error: Request was aborted.\n    at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3447)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-08T14:46:01.743Z"},{"error":"MaxFileReadTokenExceededError: File content (46461 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 CT7 (/$bunfs/root/src/entrypoints/cli.js:4309:13191)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-08T14:59:43.174Z"}]
RAW_BUFFERClick to expand / collapse

Bug Description i keep getting report that the weekly value is going up instead of session, despite "being on the session" budget, is this miss reporting ? found weird to get notices of weekly limit change in a row

Environment Info

  • Platform: darwin
  • Terminal: ghostty
  • Version: 2.1.96
  • Feedback ID: 7e6dd82d-9b2d-4983-b91b-7c515a0fb36b

Errors

[{"error":"Error: Request was aborted.\n    at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3447)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-08T14:46:01.743Z"},{"error":"MaxFileReadTokenExceededError: File content (46461 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 CT7 (/$bunfs/root/src/entrypoints/cli.js:4309:13191)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-08T14:59:43.174Z"}]

extent analysis

TL;DR

The issue might be related to incorrect budget tracking, and checking the budget configuration and request handling could provide insights.

Guidance

  • Verify the budget configuration to ensure it is set to "session" and not "weekly" to confirm the intended tracking mode.
  • Investigate the makeRequest function in cli.js to understand why requests are being aborted, which could be related to the incorrect budget tracking.
  • Consider using offset and limit parameters when reading file content to avoid MaxFileReadTokenExceededError and prevent request aborts.
  • Review the error handling mechanism to ensure it correctly reports errors and provides useful feedback instead of misleading notices.

Example

No specific code snippet can be provided without more context, but reviewing the cli.js file around lines 50 and 4309 might help in understanding the request handling and file reading logic.

Notes

The provided information lacks specific details about the budget tracking implementation, making it challenging to provide a precise fix. The errors suggest issues with request handling and file reading, which might be contributing to the incorrect budget tracking.

Recommendation

Apply workaround: Review and adjust the budget configuration and request handling logic to ensure correct tracking and error reporting, as upgrading to a fixed version is not implied in the provided information.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING