_KermanandTianyi Cui
fb79a944f5
Give durable user context its producer-owned source kind instead of a generic plugin wrapper. The V3-to-V4 conversion preserves the frozen rename and collision rules, all own JSON metadata, event coordinates, and historical request-only kinds. Native catalog and JSONL admission retain source validation so unknown attribution can survive without its producer while malformed owned sources are refused. Use an explicit user-only RequestUserInput for auxiliary LLM prompts that do not own durable message identity. Auto Review and compaction remove their request-only source registrations while retaining prompt content and freezing; provider serializers and projections keep the same wire data, assistant replay isolation, image ordering, and tool correlation. Session writes, Agent delivery, and recorded title requests continue to require identified durable messages. Bind the saved compatibility policy only to user sources and qualify tmux location attribution without weakening fixed system, model, or tool semantics. Rebuild the current inventory and unpublished V4 acknowledgement on the actual tool-role parent, preserving its rationale and all accepted historical records. The catalog format version records tooling metadata; Session remains V4. Developer-role policy and activation belong to their own feature. The latest-master Messages adapter, serialization, request-input typing, EpochHeader reservation, and attribution checks pass 103 tests across five files. The retained V3 Messages input-history snapshot passes through the source profile; Host/Client typechecks and all 41 documentation gates pass. The generated comparison records four changed roots and 447 unchanged type fingerprints. Latest-master ARIA changes are retained, with producer source labels applied independently; new Messages fixtures retain their producer names as declared source kinds and use the fixed system-message helper; recorded Session generations are unchanged by this regrouping. Co-authored-by: Tianyi Cui <[email protected]>
description, kind
| description | kind |
|---|---|
| Package map for the conversation-condensing feature family: automatic compaction, the on-demand /compact command, and tool-output trimming. | package-group |
compaction/ — compaction capability family
English | 中文
Summary
The compaction/ group keeps long agent conversations working near the model's context limit: older history is condensed into a summary automatically as token pressure builds, on demand with /compact, oversized tool outputs can be trimmed first so there is less to condense, and images an image-capable route can no longer send are replaced with placeholders. The shipped dsh base enables the feature by default — mount the packages explicitly to tune when and how condensation happens. The token measurement that decides when to condense lives in a separate LLM-family service.
Table of Contents
Packages
Each package below provides one piece of the feature; open a package page for how to use it.
| Package | Role | ctx key |
|---|---|---|
compaction/ |
The shared condensation contract: the operations and summary format every backend and trigger use | ctx.compaction |
compaction-basic/ |
Automatic condensation of older history into a summary as token pressure builds | registers ctx.compaction |
compaction-tool-result-pruner/ |
Trims oversized tool outputs so less history needs condensing | ctx.toolResultPruner |
compaction-image-offload/ |
Replaces over-budget request images with placeholders when an image-capable route rejects a request | listens to agent/request-error |
command-compact/ |
The /compact command to condense history on demand |
registers on ctx.commands |
Related documentation
Start with the subsystem reference for the shared vocabulary, then read the two Agent Notes for the design rationale.
- Compaction subsystem reference — the condensation vocabulary, results, and service behavior.
- Compaction capability-seam Agent Note — how the family is split and why it depends on session and LLM vocabulary.
- Queued manual compaction Agent Note — how on-demand
/compactserializes against running turns. - Capability seams — the Service Definition / Service Provider / Consumer split this family follows.
Dev Note
Working context for maintainers — click to expand
None.