{"version":"2.1.281","anchor":"ambient-attachments-can-be-owed-to-the-next-turn-start","canonical_anchor":"ambient-attachments-can-be-owed-to-the-next-turn-start","heading":"Ambient attachments can be owed to the next turn start","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/ambient-attachments-can-be-owed-to-the-next-turn-start","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Ambient attachments can be owed to the next turn start\n\nAmbient attachments can now be held over and delivered at the start of the next turn\n\n**Unclear.** The finding does not say which attachments count as ambient or what causes them to become owed.\n\n**What**\n\nAn attachment is extra context that Claude Code adds to a message on its own, alongside what you typed. Some of these, called ambient attachments, can now be marked as owed and delivered at the start of the next turn. A turn is one round of you sending a message and Claude answering.\n\nWhen your input is processed, Claude Code checks a new `ambientAttachmentsOwed` marker and clears it. A new step then places the owed turn-start attachments right after the first message of that turn. Attachment loading now takes a mode that is either \"all\" or unset, where before it was a simple yes or no.\n\n**Why**\n\nContext that could not be added earlier is now carried forward to the next turn.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}