fix(status): show output compression level in cce status - #154
Merged
Conversation
The output compression config key (compression.output) was wired into the MCP server but cce status didn't display it, making it impossible to verify the setting took effect. Add the output level line to cce status output, reading from state.json (which set_output_compression persists to) with config as fallback.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the cce status CLI output to surface the currently active output compression level (used by the MCP server response directive), using state.json as an override with config fallback so users can verify their setting took effect.
Changes:
- Add an
Outputline tocce statusshowing the current output compression level. - Read the output compression level from
state.json(runtime override) with config fallback.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Clamp output level to LEVELS (off/lite/standard/max) so corrupted state.json or invalid config doesn't display a bogus level. Reuse the project_storage_dir() result for both state.json and stats.json.
fazleelahhee
approved these changes
Aug 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #153.
The
compression.outputconfig key IS wired into the MCP server (via_apply_output_compression, which appends the compression directive to every tool response). The reporter's claim that it's "parsed but never read" was based on testing onlycce search, which shows raw retrieval results to a human, not AI model output.The real gap:
cce statusdidn't display the active output compression level, so users had no way to verify their setting took effect.This PR adds an
Outputline tocce statusshowing the active level, reading fromstate.json(whereset_output_compressionpersists runtime changes) with the config default as fallback.