{"version":"2.1.300","anchor":"cloud-send-file-401-gets-guidance","canonical_anchor":"cloud-send-file-401-gets-guidance","heading":"Clearer error when a cloud session cannot send a file","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/cloud-send-file-401-gets-guidance","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Clearer error when a cloud session cannot send a file\n\nA sign-in error when sending a file from a cloud session now explains that the sign-in expired and says to wait about five minutes\n\n**What**\n\nA cloud session is a Claude Code session running on a remote computer rather than your own. When sending a file from one fails with a 401 error (a \"not authorised\" reply), Claude Code now adds an explanation to the error. It says the cloud environment's sign-in has expired and tells you to wait about five minutes before trying again.\n\n**Why**\n\nYou get a cause and a next step instead of a bare error code.\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"}