Context Warning Disappears Before Reaching Zero in Version 0.2.107
Status Fixed / completed
Maintainer reply None cached
Activity 7 comments · opened May 9, 2025 · closed May 16, 2025
Bug Description
After updating to 0.2.106 I no longer see a warning when I am around 30% left with the context, it suddenly shows up when it's 'Context remaining 0%'! This is extremely inconvenient as I can no longer manage my conversation and do not get a chance to make certain changes in my plan that I was otherwise able to do to keeep future contexts relevant, it now gets lost immediately after an auto compact. I do like auto compact as I let it happen only after I've made preparations.
Environment Info
- Platform: macos
- Terminal: iTerm.app
- Version: 0.2.106
- Feedback ID: ad731315-b539-492f-b19a-29ad3954e133
7 Comments
This still an issue in 0.2.107 - it suddenly comes up with a
context low /compact to continuebut that disrupts everything! I've got a great workflow going where I track an itemized checklist in an external file to follow in between contexts. I use that instead of the compact summary as this does not capture the work fully (and without transparency into how the summaries work, I feel they eat into the _next_ context window). I'm able to prompt it accordingly when it reaches 10% or lower before my next heavy prompt.Please bring this back or make it configurable. Claude code is now unusable.
I've had to downgrade to be able to receive manageable context warnings:
npm install -g --force --prefer-online @anthropic-ai/claude-code@0.2.104I completely agree with this feedback. The ability to manage context without automatic low/compact interruptions was crucial for maintaining a consistent and efficient workflow, especially when working with structured checklists or external reference files. That control allowed for far more precision in how and when to shift context, particularly for those of us managing longer, iterative sessions with AI-driven coding tools.
Please consider reinstating this feature or making it configurable in upcoming releases. It’s a major workflow enabler, and its removal has significantly impacted usability for power users. Bringing it back would be greatly appreciated.
v0.2.113 fixes this by adding the context warning back but a major new blocker now is that that a
context is low, run /compact to continuewarning shows up even when you have 35% context remaining. The exact same prompt after downgrading to 0.2.105 works without issues. All of this started after0.2.106and each new update has had issues around context warnings / context usage.Yes, i noticed this too, quite simply, just give us the real time %% of context, let us decide what to do with that information :)
Seems to have been fixed in more recent updates
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.