Description
The DCP plugin triggers compression even when the current context usage is well below the configured minCompressionThreshold.
Observed behavior:
- DCP version: 3.1.9
minCompressionThreshold configured to 15%
- Context usage was only ~4% (40.2K tokens)
- Despite being well below the 15% threshold, compression still triggered
Steps to Reproduce
- Configure DCP with
minCompressionThreshold of 15%
- Run a session until context reaches ~4% usage
- Observe that compression triggers anyway, ignoring the configured threshold
Expected Behavior
Compression should NOT trigger automatically when the current context usage percentage is below minCompressionThreshold. The threshold should be respected as a hard minimum.
Root Cause
The minCompressionThreshold check in DCP's compression logic is not correctly guarding against automatic compression when the current usage is below the configured percentage. The threshold comparison may be using the wrong value or evaluating incorrectly.
Related
Description
The DCP plugin triggers compression even when the current context usage is well below the configured
minCompressionThreshold.Observed behavior:
minCompressionThresholdconfigured to 15%Steps to Reproduce
minCompressionThresholdof 15%Expected Behavior
Compression should NOT trigger automatically when the current context usage percentage is below
minCompressionThreshold. The threshold should be respected as a hard minimum.Root Cause
The
minCompressionThresholdcheck in DCP's compression logic is not correctly guarding against automatic compression when the current usage is below the configured percentage. The threshold comparison may be using the wrong value or evaluating incorrectly.Related