{"version":"2.1.234","anchor":"turn-update-instruction-now-asks-for-a-standalone-closing-re","canonical_anchor":"turn-update-instruction-now-asks-for-a-standalone-closing-re","heading":"Turn-update instruction now asks for a standalone closing recap","tier":"notice","area":"Turn Updates","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/turn-update-instruction-now-asks-for-a-standalone-closing-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Turn-update instruction now asks for a standalone closing recap\n\nProgress updates now end with a short recap of what was found, done and what comes next.\n\n**What**\n\nThe optional instruction that shapes progress updates during a turn used to say the final message should stand on its own for a reader catching up. It now asks for a short recap naming what was found, what was done and what is next, so the last message alone tells the whole story.\n\n**Details**\n\n- Active only when the environment variable `CLAUDE_CODE_TURN_UPDATES` is set, or when the model capability for turn updates arrives with the session's client data.\n\n**Evidence**\n\n`Close with a short recap that stands on its own`\n\n- Area: Turn Updates\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}