{"version":"2.1.274","anchor":"stage-file-remote-session-uploadoutput-can-be-invoked-wit","canonical_anchor":"stage-file-remote-session-uploadoutput-can-be-invoked-wit","heading":"Stage-file (remote session upload\/output) can be invoked without CLAUDE_CODE_REMOTE_SESSION_ID via a 'vouched' path","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/stage-file-remote-session-uploadoutput-can-be-invoked-wit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Stage-file (remote session upload\/output) can be invoked without CLAUDE_CODE_REMOTE_SESSION_ID via a 'vouched' path\n\nRemote-session file staging can now skip the session-ID requirement via a new 'vouched' path\n\n**What**\n\nThe function that stages files for upload or output in a remote session now accepts a second, optional parameter. When it's set, file staging can proceed without the usual `CLAUDE_CODE_REMOTE_SESSION_ID` requirement, and the mount is marked as \"vouched\" instead of tied to an actual remote session ID. This path is refused for synced, filestore-backed documents, with the message \"synced documents are not staged here.\"\n\n**Why**\n\nThis adds a way to stage files in remote-session contexts without a real session ID present, while still excluding documents that are synced through the filestore, which need to go through their normal path instead.\n\n- Area: Sessions\n- Names: `CLAUDE_CODE_REMOTE_SESSION_ID`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}