Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Session StatusArea: what it touches
Internal ChangesKind: in v2.1.323,
Internal ChangesSection of the release
What
Claude Code tracks whether a session is busy, waiting or idle. It already counted work blocked on a nested prompt as waiting. It now also counts a wait on the critical path, the work the session cannot move past until it finishes, in the same way.
These waits are logged but follow a slightly different rule for resuming. Setting CLAUDE_CODE_DISABLE_NESTED_CHAIN_IDLE still turns this tracking off.
Why
This affects when a session reports itself as waiting or idle, which can matter to anything that reacts to that state.
