Skip to content

Coder Agents compaction: decide 100% opt-out and override threshold semantics #30203

Closed as not planned

Description

@ibetitsmike

Note

Xum (an AI agent) opened this issue on Mike's behalf to track two design questions raised in review of #28568. Both are pending a maintainer decision; this issue does not record owner acceptance.

#28568 makes Coder Agents compact a chat at whichever of two triggers is reached first:

  • Chat trigger: the member's threshold (or the chat model's default) against the chat model's window.
  • Organization override trigger: the organization compaction model's own compression_threshold against that model's window.

Review raised two questions about this design.

1. Should a personal threshold of 100% opt out of all automatic compaction?

Review thread: #28568 (comment) (CRF-11)

  • On main: a threshold of 100 turns off automatic compaction for that model.
  • With feat: trigger compaction independently for the chat and compaction models #28568: 100 turns off only the chat trigger. When the organization has an enabled compaction override, chats with that model still compact at the override's point. The settings page states this ("Setting 100% turns off that model's own compaction threshold. An organization override may still compact chats with that model.").
  • Alternative raised in review: when the chat trigger is disabled, do not fire the override trigger either.

2. Should the compaction model's own threshold be the organization trigger?

Review thread: #28568 (comment) (CRF-13)

  • With feat: trigger compaction independently for the chat and compaction models #28568: the override model's compression_threshold sets the organization-wide trigger, and a value of 100 makes chats summarize with their own model instead of the override. The model form describes the field only as "Percentage at which context is compressed."; the Coder Agents settings page explains the organization effect.
  • Alternatives raised in review:
    • Give the compaction override its own threshold setting.
    • Keep a single chat trigger and check at summary time that the history fits the summarizer's window.
    • At minimum, note on the model form that the model is the organization's compaction model.

Decision needed

For each question, keep the #28568 behavior or change it. Any change would land as a follow-up PR.

Activity

  1. linear-code commented on Sep 30, 2026

    @linear-code
  2. ibetitsmike commented on Oct 3, 2026

    @ibetitsmike
    CollaboratorAuthor

    Xum (an AI agent) posted this on Mike's behalf, recording Mike's maintainer decision.

    Decision: keep the #28568 behavior for both questions. No follow-up PR is planned.

    1. 100% opt-out (CRF-11): keep. A personal threshold of 100% turns off only that model's chat trigger. When the organization has an enabled compaction override, chats with that model can still compact at the override's threshold. The settings page already says so.
    2. Override model's threshold as the organization trigger (CRF-13): keep. The organization override model's own compression_threshold sets the organization trigger, and a value of 100 makes chats summarize with their own model. The model form copy stays as it is; the Coder Agents settings page explains the organization effect.
  3. ibetitsmike commented on Oct 9, 2026

    @ibetitsmike
    CollaboratorAuthor

    Xum (an AI agent) posted this on Mike's behalf, recording Mike's maintainer decision.

    Update: question 2 (CRF-13) is reversed. The earlier decision to keep the override model's own compression_threshold as the organization trigger no longer stands.

    The summarizer's limit is its context window, not a percentage someone set on the model. #28568 now compacts at a fixed 80% of the override model's window, which leaves 20% for the summary prompt and the summary:

    • The override model's own compression_threshold is ignored for compaction, including 100%. An override at 100% is no longer treated as absent.
    • An override that is unset, disabled, without usable credentials for the member, or with an unknown context window still falls back to the chat model.
    • The member's threshold still applies to the chat model's window, and the lower of the two points binds.
    • The over-limit error for a binding override now asks an administrator to choose an override model with a larger context window, instead of raising its threshold.

    Question 1 (CRF-11, personal 100%) is unchanged: a personal 100% turns off only the chat trigger.

  4. ibetitsmike commented on Oct 9, 2026

    @ibetitsmike
    CollaboratorAuthor

    Xum (an AI agent) closed this issue on Mike's behalf.

    Both questions are settled in #28568.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions