{"version":"2.1.232","anchor":"over-context-warnings-distinguish-a-hard-limit-from-the-comp","canonical_anchor":"over-context-warnings-distinguish-a-hard-limit-from-the-comp","heading":"Over-context warnings distinguish a hard limit from the compaction window","tier":"notice","area":"Compaction","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/over-context-warnings-distinguish-a-hard-limit-from-the-comp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Over-context warnings distinguish a hard limit from the compaction window\n\nOver-context warnings now distinguish a hard token limit from the compaction window.\n\n**What**\n\nWhen the conversation is over budget, the warning now says which kind of limit was hit: a hard token limit produces the \"Context exceeds the N-token limit\" wording, and anything else produces the compaction-window wording.\n\n**Details**\n\n- The same distinction is exposed to tooling as an over-limit object carrying how many tokens over you are and which kind it is.\n- The field is documented as describing how the window was resolved, not as a prediction of whether the API will accept the request.\n\n**Evidence**\n\n`\"Present when total_tokens exceeds raw_max_tokens. kind says how the window was resolved`\n\n- Area: Compaction\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}