{"version":"2.1.314","anchor":"bridge-withdraw-pictures-and-write-late-arriving-attachment","canonical_anchor":"bridge-withdraw-pictures-and-write-late-arriving-attachment","heading":"Images can be withdrawn from a conversation, and late file uploads report what happened","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/bridge-withdraw-pictures-and-write-late-arriving-attachment","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Images can be withdrawn from a conversation, and late file uploads report what happened\n\nIn bridge sessions, images can be pulled from the transcript, and Claude is told when a late upload was not saved or was moved\n\n**What**\n\nA bridge session is one where Claude Code is driven from somewhere else, such as a remote client. Image attachments in these sessions can now be withdrawn from the transcript (the record of the conversation). When that happens, the message's images are replaced with a placeholder.\n\nFiles uploaded after a message was sent now report two more outcomes to Claude through a task notification:\n\n- not saved, when the file was not written\n\n- moved, when the file went somewhere other than expected\n\nMessages also keep track of which files were saved and which images they carry.\n\n**Why**\n\nRemote and bridge sessions can now take back images that were shared, and Claude learns what actually happened to files that arrived late instead of assuming they were saved.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}