{"version":"2.1.227","anchor":"context-indicator-can-follow-a-worker-s-own-auto-compact-set","canonical_anchor":"context-indicator-can-follow-a-worker-s-own-auto-compact-set","heading":"Context indicator can follow a worker's own auto-compact settings","tier":"notice","area":"Compaction","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/context-indicator-can-follow-a-worker-s-own-auto-compact-set","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Context indicator can follow a worker's own auto-compact settings\n\nThe context indicator can use a remote worker's real auto-compact settings so the countdown matches reality.\n\n**What**\n\nA 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.\n\n**Details**\n\n- 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.\n- Adoption is reported as `tengu_remote_autocompact_state_adopted`.\n\n**Evidence**\n\n`Worker-resolved auto-compact state, emitted by CCR workers at boot`\n\n- Area: Compaction\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}