September 2026 Release
September 2026 expands what peers can do with files in Studio. Alongside downloadable flow outputs in replies, peers can now store sandbox files and use generic Word templates, making file-based workflows easier to build without any migration or special upgrade action.
Developers maintaining custom applications should use the Developer Hub for API, SDK, package, and migration notes.
Highlights
- Files produced during a flow run now appear as attachments on peer replies.
- Users can download generated files directly from the conversation.
- Peers can now store sandbox files for file-based workflows.
- Generic Word templates are now supported for peer tooling.
- No migration or special upgrade step is required for this release.
New in Studio
- When a flow-based peer generates files as part of a run, Studio now includes those files on the reply as downloadable attachments.
- Generated outputs are surfaced in the conversation where the reply appears, making them easier to find and use.
- Peers can now store sandbox files, adding file handling support inside peer workflows.
- Generic Word templates are now supported, expanding the kinds of document-based tools peers can use.
- This update improves the handoff from flow execution to end-user review of generated artifacts and broadens file-based peer capabilities.
For organization admins
- Teams using peers for document-heavy workflows can now work with sandbox files and generic Word templates in addition to downloading generated flow outputs from replies.
- No rollout planning, migration, or special upgrade action is required for this release.
For developers
- Review peer experiences that generate files and confirm the attached outputs appear as expected in replies.
- If your peers rely on file handling or document generation, test sandbox file storage and generic Word template behavior after upgrading.
- Use the Developer Hub for technical implementation details and API guidance.
What to try
- Run a flow-based peer that generates a file and confirm the reply includes it as an attachment.
- Download the attached file from the conversation and confirm it matches the generated output.
- Open a peer workflow that uses sandbox files and confirm files can be stored and used as expected.
- Test a peer workflow that uses a generic Word template and confirm the document output matches the template.