{"version":"2.1.281","anchor":"on-resume-split-assistant-responses-are-regrouped-behind-t","canonical_anchor":"on-resume-split-assistant-responses-are-regrouped-behind-t","heading":"On resume, split assistant responses are regrouped, behind tengu_foamy_spring (defaults on)","tier":"notice","area":"Resume","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/on-resume-split-assistant-responses-are-regrouped-behind-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### On resume, split assistant responses are regrouped, behind tengu_foamy_spring (defaults on)\n\nWhen a conversation is resumed, messages that were split away from the response they belong to are moved back next to it\n\n**What**\n\nResuming means reopening an earlier conversation and carrying on. When Claude Code loads the transcript of a resumed conversation, it now looks for messages that belong to a particular response but ended up in the wrong place. These include tool results and other messages attached to a turn. It moves them back beside the response they belong to. The step runs behind `tengu_foamy_spring`.\n\nWhen anything is moved, Claude Code records `tengu_resume_split_response_regrouped` with counts of the responses regrouped and the rows moved. If the step hits an error, it logs the error and leaves the conversation as it was.\n\n**Why**\n\nA resumed conversation is put back into its proper order before it continues. If the regrouping fails, the conversation is still resumed unchanged.\n\n- Area: Resume\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}