Automatic compaction passes more context when rebuilding attachments and handles failures on a dedicated path.
What's wrong with this entry?
The reactive-compaction path passes more context into attachment building and handles failures through a dedicated path.
- The attachment builder is now called with the message list and an agent-context descriptor in addition to its previous arguments.
- Errors go through a dedicated handler rather than a generic catch that logged and returned empty attachments.
reactive_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.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