You'll notice
Memory-pressure warning now shows separate 'high' and 'critical' banners instead of one combined one
What
The 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.
Why
Splitting 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.