{"version":"2.1.299","anchor":"bridge-attachment-downloads-stricter-size-and-quiet-limits","canonical_anchor":"bridge-attachment-downloads-stricter-size-and-quiet-limits","heading":"Attachment downloads get a size cap, a stall limit and a sign-in retry","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/bridge-attachment-downloads-stricter-size-and-quiet-limits","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Attachment downloads get a size cap, a stall limit and a sign-in retry\n\nAttachment downloads in bridge sessions are capped at about 35 MB, stop if they stall, and retry once after a refused sign-in\n\n**What**\n\nWhen Claude Code downloads attachments ahead of time in a bridge session, the download now works differently:\n\n- Size: downloads are capped at 36,700,160 bytes (35 MB).\n\n- Stalls: a download stops if no data arrives for too long, replacing the old deadline for the server's first reply.\n\n- Sign-in: if the server rejects the sign-in (a 401 error), Claude Code refreshes its sign-in token once and tries again.\n\n- Results: each download now records timing details, and a new outcome, `inlined_image_not_saved`, covers an image that was included directly but not saved.\n\n**Why**\n\nAttachments are more likely to arrive after an expired sign-in, and slow or oversized downloads are cut off in a clearer way.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}