{"version":"2.1.305","anchor":"compaction-skips-tool-search-when-sticky-betas-already-cover","canonical_anchor":"compaction-skips-tool-search-when-sticky-betas-already-cover","heading":"Compaction checks the session's fixed beta features before picking its tools","tier":"internal","area":"Compaction","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/compaction-skips-tool-search-when-sticky-betas-already-cover","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Compaction checks the session's fixed beta features before picking its tools\n\nThe check that decides which tools go with a compaction request now also looks at beta features fixed for the session's main model\n\n**Unclear.** It is not clear what this extra check changes in practice for a compaction request.\n\n**What**\n\nCompaction is how Claude Code shrinks a long conversation into a summary, and it sends its own request to the model for that. When deciding which tools to include in that request, Claude Code now also checks the beta features that stay attached to the session for the main model. Beta features are optional capabilities switched on for a request.\n\n**Why**\n\nThis can change which tools the compaction request carries, which can affect how much of an earlier request the model can reuse.\n\n- Area: Compaction\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}