{"version":"2.1.239","anchor":"remote-file-staging-can-now-write-under-outputs","canonical_anchor":"remote-file-staging-can-now-write-under-outputs","heading":"Remote file staging can now write under \/outputs\/","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/remote-file-staging-can-now-write-under-outputs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Remote file staging can now write under `\/outputs\/`\n\nRemote sessions can now stage writable files under \/outputs\/, not just \/uploads\/.\n\n**What**\n\nOn managed remote sessions, staged files can be written to paths under `\/outputs\/` and are writable (mode 420) rather than read-only. Previously only `\/uploads\/` was accepted. Adding a directory is still limited to `\/uploads\/`.\n\n**Details**\n\n- Restricted to sessions whose remote-session id and environment kind mark them as managed; on any other runner the attempt is rejected with a specific error code.\n- Skips the write when the local copy is already newer, sweeps its temporary files, and reports through its own telemetry channel.\n\n**Evidence**\n\n`staging under \/outputs\/ is only supported on managed remote sessions`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}