The current threshold for context length warning is too low

Resolved 💬 2 comments Opened Aug 12, 2025 by sobri909 Closed Aug 12, 2025

At some point it was lowered to ... 20%? But that's the point at which I typically start the wrap up process on a work session (dev log updating, knowledge file updating, etc). I need warning before that point, not at that point.

I just had a work session go from no warning to a warning of "Context low (7% remaining)" (presumably due to pasting in a large chunk of console logs). That's not workable. At 7% I'm basically f*cked. There's not enough context length to do the necessary documentation. I needed to know far earlier, so that I could be aware that a large paste would push me over the boundary of remaining tokens I need.

If the instinct is to reply with "just use /compact"... no. The fresh context doesn't get enough information to continue reliably. The compact system is great, I'm really impressed by it, but it's not adequate for my workflows. When context limit is reached I need to have full documentation to md files that fits my workflow/project requirements, and then I start a new fresh session, instructing the model to read docs and logs and tell me what it understands before we can proceed with the new work session. The /compact flow is informal, opaque, and inadequate (for me).

So yeah, a long rambling way of saying: I want the warning threshold back how it was before. Or to be configurable. The current lower threshold puts me at too much risk of ... needing to say words with asterisks in them.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗