{"version":"2.1.282","anchor":"prompt-snapshots-now-record-wire-shape-echowiretoolinputs-a","canonical_anchor":"prompt-snapshots-now-record-wire-shape-echowiretoolinputs-a","heading":"Saved sessions now record their request layout and carry it into a resume","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/prompt-snapshots-now-record-wire-shape-echowiretoolinputs-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Saved sessions now record their request layout and carry it into a resume\n\nSession snapshots now save the request layout, raw tool-input echo choice and context placement, and restore them when you resume\n\n**Unclear.** What each saved layout field changes in the actual request sent to the model is not settled.\n\n**What**\n\nThe option to echo raw tool inputs, and details of how each request to the model is laid out, are now saved in the session's prompt snapshot instead of being decided afresh. The snapshot records:\n\n- the request layout: how system turns, tool changes, tools and kept reminders are placed\n\n- whether raw tool inputs are echoed back\n\n- whether context is announced or placed inline\n\nThese are carried forward when a session is resumed, and Claude Code records an event each time they are saved. The remote switch behind this falls back to on in the code, including when no switch can be read.\n\n**Why**\n\nA resumed session should send requests laid out the same way as when it started, so its behaviour stays consistent and prompt caching (reusing the already-processed start of a conversation) keeps working.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}