The context indicator can use a remote worker's real auto-compact settings so the countdown matches reality.
What's wrong with this entry?
A remote worker can now publish the auto-compact configuration it actually resolved, and the context-usage indicator will use that instead of working it out locally. This makes "% until auto-compact" count down to the point compaction really happens, and switches to "% context used" when the worker says the threshold is not enforced. It only applies when a connected worker sends the frame, and the message is marked internal.
- The message carries whether auto-compact is enabled, the effective context window, the threshold, whether it is enforced, and where the setting came from: environment, settings, client data, experiment, model default, unknown model, or auto.
- Adoption is reported as
tengu_remote_autocompact_state_adopted.
Worker-resolved auto-compact state, emitted by CCR workers at boot
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.239
Skill text carried through compaction is no longer mistaken for a live request
Both mention compaction
-
v2.1.247
Summarizing uses the same prompt assembly as the rest of the conversation
Both mention compaction
-
v2.1.247
Compaction builds its system prompt with the shared assembler
Both mention compaction