claude-code - 💡(How to fix) Fix [Bug] Session token limit exhausted prematurely on step continuation [1 comments, 2 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#55029Fetched 2026-05-01 05:48:06
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×4commented ×1
RAW_BUFFERClick to expand / collapse

Bug Description Armé un plan de ejecución con claude, invertí tiempo y tokens en que el plan quede lo suficientemente claro y que la ejecución sea mas sencilla. Ayer, con el limite de tokens de toda una sesion, quedó en la mitad de la ejecutción de un step, que debería ser sencillo de implementar, pues no es demasiado largo ni complejo, hoy le pedí que continúe la ejecución que quedó cortada a la mitad, y en menos de 10 minutos y se agotaron los tokens de la sesión y tampoco terminó. Utilicé /compact antes de iniciar la ejecución del step, la instrucción ayer fue: ejecuta la siguiente parte del plan, hoy simplemente le pedí que continue y ya llevo el limite de 2 sesiones, ustilizando sonnet 4.6 en medium effort, y todavía no termina 1 step! qué está pasando? estoy pagando por un servicio que estoy utilizando 10 minutos cada 4 horas, es inaudito!

Environment Info

  • Platform: win32
  • Terminal: vscode
  • Version: 2.1.123
  • Feedback ID: 6c7cc72c-9422-4bca-8ba8-136822f67929

extent analysis

TL;DR

The issue is likely due to the token limit being reached too quickly, causing the execution to be cut off, and a potential solution is to optimize the plan or adjust the token limit settings.

Guidance

  • Review the plan and simplify it to reduce the number of tokens required for execution.
  • Consider using a more efficient version of the tool or adjusting the effort level to reduce token usage.
  • Check if there are any settings or configurations that can be adjusted to increase the token limit or optimize performance.
  • Verify if the issue is specific to the current version (2.1.123) and if updating to a newer version could resolve the problem.

Notes

The issue seems to be related to the token limit and the efficiency of the plan, but without more information about the specific plan and the tool being used, it's difficult to provide a more detailed solution.

Recommendation

Apply workaround: Optimize the plan and adjust token limit settings to reduce token usage and prevent the limit from being reached too quickly.

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

claude-code - 💡(How to fix) Fix [Bug] Session token limit exhausted prematurely on step continuation [1 comments, 2 participants]