{"version":"2.1.318","anchor":"bridge-attachment-deleted-copy-tracking","canonical_anchor":"bridge-attachment-deleted-copy-tracking","heading":"Reporting on deleted attachment copies sent over the bridge is more detailed","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/bridge-attachment-deleted-copy-tracking","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Reporting on deleted attachment copies sent over the bridge is more detailed\n\nReports on deleted attachment copies over the bridge now name seven failure reasons and use per-type size thresholds\n\n**Unclear.** It is not clear whether these checks only produce reports or can also stop an attachment from reaching a remote session.\n\n**What**\n\nThe bridge is the connection Claude Code uses for remote sessions. When an attachment sent over it has a copy that gets deleted, Claude Code reports on it. That reporting now tells apart these failure reasons:\n\n- `copy_late`: the copy came too late\n\n- `copy_not_stored`: the copy was not stored\n\n- `copy_failed`: making the copy failed\n\n- `copy_too_small`: the copy was too small\n\n- `copy_unusable`: the copy could not be used\n\n- `copy_is_original`: the copy was the original file\n\n- `copy_cut_short`: the copy was cut short\n\nThe size check uses a threshold of 150 for PNG images and 50 for other file types.\n\n**Why**\n\nThis is about checking and reporting on attachments that pass through remote sessions.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}