{"version":"2.1.307","anchor":"streamed-json-fold-copies-settled-on-stream-events-and-compa","canonical_anchor":"streamed-json-fold-copies-settled-on-stream-events-and-compa","heading":"Change to how progress entries are recorded when running without an interface","tier":"internal","area":"Session Transcripts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/streamed-json-fold-copies-settled-on-stream-events-and-compa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Change to how progress entries are recorded when running without an interface\n\nWhen Claude Code streams JSON output, progress and attachment entries are now kept as provisional copies and finalised at set points\n\n**Unclear.** It is not shown whether this changes anything a user sees in the output or the transcript.\n\n**What**\n\nWhen Claude Code runs without an interactive interface and streams its output as JSON, it records progress entries and attachments in its transcript, the running record of the session. It now keeps provisional copies of these entries and finalises them when stream events arrive, when the status changes and when a command starts. Before, they were recorded directly.\n\n**Why**\n\nThis changes how progress entries are written to the transcript.\n\n- Area: Session Transcripts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}