{"version":"2.1.312","anchor":"interrupted-turn-resume-re-run-pending-agent-calls","canonical_anchor":"interrupted-turn-resume-re-run-pending-agent-calls","heading":"Resuming an interrupted turn re-runs waiting agent calls instead of the whole turn","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/interrupted-turn-resume-re-run-pending-agent-calls","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Resuming an interrupted turn re-runs waiting agent calls instead of the whole turn\n\nAfter a restart, agent calls left waiting in an interrupted turn are run again so each picks up its agent, rather than redoing the whole turn\n\n**Unclear.** It is not clear what makes this resume path run, so it may not take effect in every session.\n\n**What**\n\nA turn is one round of Claude working on your request. An Agent call is when Claude hands part of the work to a separate helper agent. If Claude Code restarts while a turn is interrupted and that turn had Agent calls still waiting, the session now runs those calls again so each one resumes the agent it was waiting on. Before, Claude Code went straight to resuming the interrupted turn as a whole.\n\n- Each resumed agent keeps its original call and the message that made it.\n\n- If Claude Code cannot find all of the waiting calls, it resumes without them.\n\n**Why**\n\nWork that helper agents had already started can carry on after a restart instead of being thrown away and started again.\n\n- Flag `tengu_eager_pillow`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.312; this account: on, anonymous baseline: on, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}