Setting or clearing DISABLE_COMPACT now takes effect immediately, not just at startup.
What's wrong with this entry?
The auto-compact suggestion and the /compact command read DISABLE_COMPACT from the environment each time they are checked, instead of a snapshot taken at startup. Setting or clearing it during a session now changes behaviour immediately.
- Decides whether the context-limit banner offers "/clear to continue" or "/compact or /clear to continue".
- The value goes through a truthiness helper at the point of use.
- Separately, a startup check that read
CInow passes a literal false.
/compact or /clear to continue, Context exceeds the ${l}-token limit by ${t} tokens, Free up context by summarizing the conversation so far, process.env.DISABLE_COMPACT
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
1M-context and compaction checks now go through model capability lookup
Both mention disable compact compaction
-
v2.1.219
Post-compaction file restore skips memory files
Both mention compaction
-
v2.1.219
Tool-result eviction no longer double-counts already-seen results
Both mention compaction