{"version":"2.1.323","anchor":"critical-path-waits-count-as-blocked-chains-for-idle-state","canonical_anchor":"critical-path-waits-count-as-blocked-chains-for-idle-state","heading":"Waits on the critical path now count toward a session's idle state","tier":"internal","area":"Session Status","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/critical-path-waits-count-as-blocked-chains-for-idle-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Waits on the critical path now count toward a session's idle state\n\nClaude Code now counts critical-path waits as blocked work when deciding whether a session is idle\n\n**What**\n\nClaude 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.\n\nThese waits are logged but follow a slightly different rule for resuming. Setting `CLAUDE_CODE_DISABLE_NESTED_CHAIN_IDLE` still turns this tracking off.\n\n**Why**\n\nThis affects when a session reports itself as waiting or idle, which can matter to anything that reacts to that state.\n\n- Area: Session Status\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}