{"version":"2.1.238","anchor":"files-changed-during-a-turn-are-uploaded-to-the-cloud-sessio","canonical_anchor":"files-changed-during-a-turn-are-uploaded-to-the-cloud-sessio","heading":"Files changed during a turn are uploaded to the cloud session worker","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/files-changed-during-a-turn-are-uploaded-to-the-cloud-sessio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Files changed during a turn are uploaded to the cloud session worker\n\nCloud sessions now upload files you changed during a turn back to the session worker.\n\n**What**\n\nCloud sessions gained an outputs push: after a turn, files under the outputs root that were modified since the turn started are read and POSTed to the session worker under a `\/outputs` path. It runs only when a remote session id is set and the environment is `anthropic_cloud`, and the server can switch it off.\n\n**Details**\n\n- Symlinks and files with more than one hard link are skipped; each file is capped at 20 MB.\n- Content is sent base64-encoded, authenticated with a session JWT.\n- A 501 or 404 from the worker is treated as the feature being off and aborts the whole pass.\n- Requires `CLAUDE_CODE_REMOTE_SESSION_ID` and `CLAUDE_CODE_ENVIRONMENT_KIND` set to `anthropic_cloud`; completion is reported as `tengu_outputs_push_completed`.\n\n**Evidence**\n\n`tengu_outputs_push_completed`\n\n- Area: Cloud Sessions\n- Names: `\/outputs`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}