Remote sessions now use the host's auto-compact settings for context and token display.
What's wrong with this entry?
A session running over the SDK or bridge can now be told the host's auto-compact configuration (whether it is on, the effective context window, the threshold, and whether it is enforced) and will use it for its own token-usage and context display, instead of guessing from local settings. A seed value can also arrive at session start.
- Carried as a new control frame type
autocompact_state, stored in app state asremoteAutocompactState. - Successful adoption is reported as
tengu_remote_autocompact_state_adopted, includingenabled,enforced,sourceandvia. - Frames that do not parse are dropped once, with the log line "[sdkMessageAdapter] Dropping malformed autocompact_state frame" and an
invalid_frameerror report. - The session state object gained
onAutocompactInputsChangedandonConversationResetcallbacks, which fire when the compaction window, model or settings change.
tengu_remote_autocompact_state_adopted, [sdkMessageAdapter] Dropping malformed autocompact_state frame
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