{"version":"2.1.315","anchor":"task-file-upload-egress-blocked-result","canonical_anchor":"task-file-upload-egress-blocked-result","heading":"Requests using your saved login are marked, and task uploads report blocked network access","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/task-file-upload-egress-blocked-result","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Requests using your saved login are marked, and task uploads report blocked network access\n\nUploads, cloud session bundles and auth checks now mark requests made with your saved login, and task uploads report egress_blocked when the network refuses\n\n**What**\n\nWhen Claude Code uses the login token it saved for you, it now marks the request with `isStoredLogin` in several places:\n\n- Requests sent for health and sign-in checks include `isStoredLogin: true` when they use the stored login token.\n\n- Creating a cloud session passes `isStoredLogin` with the bundle upload. It is true unless the console-profile path is in use. The error \"Cloud sessions require a claude.ai login. Run \/login to authenticate.\" is unchanged.\n\n- Task file uploads pass `isStoredLogin: true`.\n\n- When a task file upload fails because outgoing network traffic was blocked, the result now has the code `egress_blocked`. Before, every failure was reported as `upload_network`.\n\n**Why**\n\nIn sandboxed or network-restricted setups, a failed task upload now says the network blocked it instead of reporting a generic network failure, which points you at the actual cause.\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"}