{"version":"2.1.318","anchor":"collapsed-readsearch-grouping-gated-by-a-feature-check","canonical_anchor":"collapsed-readsearch-grouping-gated-by-a-feature-check","heading":"Collapsed file reads and searches can be grouped into running counts","tier":"notice","area":"Terminal UI","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/collapsed-readsearch-grouping-gated-by-a-feature-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Collapsed file reads and searches can be grouped into running counts\n\nWhen a feature check passes, collapsed file reads and searches are gathered into one open group that counts them, instead of one line each\n\n**Unclear.** It is not clear what decides the feature check or whether it passes for anyone.\n\n**What**\n\nA tool call is one action Claude takes, such as reading a file or searching your code. Claude Code already collapses runs of these into a compact display. When a feature check passes, it now keeps an open group that counts how many searches and reads happened, rather than adding each call to the display on its own. When the check does not pass, the display works as it did before.\n\n**Why**\n\nThis may change how runs of reads and searches look in your conversation, with a single counted group instead of separate entries.\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}