{"version":"2.1.274","anchor":"memory-pressure-banner-split-into-separate-high-and-criti","canonical_anchor":"memory-pressure-banner-split-into-separate-high-and-criti","heading":"Memory-pressure banner split into separate 'high' and 'critical' tiers","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/memory-pressure-banner-split-into-separate-high-and-criti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Memory-pressure banner split into separate 'high' and 'critical' tiers\n\nMemory-pressure warning now shows separate 'high' and 'critical' banners instead of one combined one\n\n**What**\n\nThe hook that checks memory usage and warns the user used to return a single status. It now takes a threshold and a flag for whether to emit telemetry, and runs twice: once to check the 'high' tier and once for the 'critical' tier, each producing its own banner in the interface. The `tengu_memory_threshold_crossed` telemetry event now only fires from the critical-tier check.\n\n**Why**\n\nSplitting the warning into two tiers lets Claude Code distinguish a milder heads-up (high memory use) from a more urgent one (critical), rather than treating both the same way, while only counting the more severe crossing in telemetry.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}