Give users explicit control over automatic context compression

Status Fixed / completed
Maintainer reply None cached
Activity 1 comment · opened Jul 26, 2026 · closed Aug 20, 2026

Summary

Please add a user-facing control (setting/toggle) to disable or opt out of automatic mid-session context compression, rather than having it trigger unconditionally as the context window fills.

Motivation

I work across long-running, multi-session technical projects where session context carries critical, hard-to-reconstruct detail (design decisions, debugging history, hardware/firmware state, rationale behind non-obvious choices). Losing that detail to an automatic summarization pass mid-session is a real cost for this kind of work, even when I'm keeping durable notes (handoff docs, memory files) on the side.

To be clear: I understand why compression exists and the tradeoffs involved (context window limits, cost, latency). This isn't a request to remove the feature or a misunderstanding of its purpose. The request is specifically that this should be my choice — an explicit on/off control — rather than automatic, silent behavior I have no way to disable.

Requested behavior

  • A setting (e.g. in settings.json, or a /config option) to disable automatic context compression for a session or globally.
  • If disabling isn't feasible for technical reasons, alternatives that would also address the core need:
  • A clear warning/prompt before compression happens, with a chance to opt out for that instance.
  • A way to increase the threshold at which compression triggers.
  • Some persisted, inspectable record of exactly what was summarized/dropped, so users can recover detail if needed.

Context

Raised via a Claude Code session (non-interactive) where the user asked for this feedback to be relayed after expressing strong dissatisfaction with the current all-or-nothing automatic behavior.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗