{"version":"2.1.287","anchor":"bridge-attachment-download-cleanup-and-cap-changes","canonical_anchor":"bridge-attachment-download-cleanup-and-cap-changes","heading":"Downloaded bridge attachments are cleaned up one file at a time past a set count","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/bridge-attachment-download-cleanup-and-cap-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Downloaded bridge attachments are cleaned up one file at a time past a set count\n\nAbove a set number of attachments, Claude Code now cleans up each downloaded attachment on its own instead of all of them at the end\n\n**Unclear.** What the attachment count limit is, and what it is meant to protect against, is not known.\n\n**What**\n\nWhen Claude Code downloads file attachments for a session through its bridge connection, it now cleans up each file separately once the number of attachments goes over a fixed limit. Before, cleanup ran once at the end over every attachment together.\n\nThe usage data Claude Code records about these downloads also gained two new fields. One records whether a related setting was on. The other counts attachments that were queued ahead of the files.\n\n**Why**\n\nThis changes how attachments arriving over the bridge are handled and what Claude Code reports about them.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}