{"version":"2.1.299","anchor":"file-download-retries-once-after-a-401","canonical_anchor":"file-download-retries-once-after-a-401","heading":"Session file downloads now retry once after a sign-in error","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/file-download-retries-once-after-a-401","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Session file downloads now retry once after a sign-in error\n\nA session file download refused with a 401 error is now retried once after Claude Code refreshes its sign-in\n\n**What**\n\nWhen Claude Code downloads a file for a session, such as an attachment, and the server answers with HTTP 401 (meaning the sign-in was not accepted, often because it expired), Claude Code now refreshes its sign-in and tries again. Before, it tried only once.\n\nOther changes to downloads:\n\n- The size limit differs depending on whether the file comes with a sha256 checksum (a fingerprint used to check the file).\n\n- When saving a file fails, Claude Code records what went wrong and at which step.\n\n- When an image sent inside a message cannot be saved to disk, the image is still passed along.\n\n- Retries and recoveries are counted in usage data.\n\n**Why**\n\nIn long remote sessions where the sign-in expires partway through, fewer attachments should be lost.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}