{"version":"2.1.234","anchor":"sdk-hosted-sessions-can-upload-attachments-with-a-clearer-me","canonical_anchor":"sdk-hosted-sessions-can-upload-attachments-with-a-clearer-me","heading":"SDK-hosted sessions can upload attachments, with a clearer message when they cannot","tier":"notice","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/sdk-hosted-sessions-can-upload-attachments-with-a-clearer-me","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### SDK-hosted sessions can upload attachments, with a clearer message when they cannot\n\nSDK-hosted sessions can now upload attachments, with a clearer message when files stay local.\n\n**What**\n\nAttachment uploads used to work only through the local REPL connection. Sessions hosted by the SDK can now upload too, behind the `tengu_async_goblet` flag (defaults on when the server says nothing). When output is being rendered locally and files could not be delivered, the model is now told the files are only visible in the desktop app on this machine instead of the generic \"could NOT be delivered\" wording.\n\n**Details**\n\n- Upload routing is now a named lane rather than a yes\/no: `repl`, `env_brief_upload`, `env_ccr`, `env_byoc`, `sdk_hosted`, `sdk_hosted_disabled` or `none`.\n- With the flag off, the lane becomes `sdk_hosted_disabled` and the upload does not happen.\n\n**Evidence**\n\n`only visible in the desktop app on this machine`\n\n- Flag `tengu_async_goblet`: Not enough to say (read for one account on one subscription tier against v2.1.234; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Area: SDK\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}