June 2026 Release
The June 2026 release adds a SharePoint Online datasource, brings OCR to more datasource types, exposes the agent-to-agent (A2A) protocol as a channel, and refreshes Studio's visual design.
Developers maintaining custom applications should use the Developer Hub for API, SDK, package, and migration notes.
Highlights
- New SharePoint Online datasource.
- OCR can now be enabled per datasource, across most file-based source types.
- New A2A channel exposes a Peer as a remote agent endpoint.
- Run history can be exported in multiple formats.
- Visual refresh across Peer, report, and settings screens; dark theme removed.
New in Studio
SharePoint Online datasource
A new datasource connects to SharePoint Online document libraries, with support for selecting multiple libraries and syncing per-file permissions alongside content.
See Data Sources.
Datasource OCR
OCR can now be turned on per datasource, with a choice of provider (including Tesseract and several vision-capable models) and language selection. It is available across most file-based datasource types — including S3, Azure Blob, Azure DevOps, Bitbucket, file uploads, GitHub, GitLab, QDMS, and web sources.
A2A channel
A Peer can now be exposed through the Agent-to-Agent (A2A) protocol, so another agent can discover it and send it requests. Access is secured with a workspace API token.
See A2A (agent-to-agent).
Run export
Run history can be exported in a range of formats — including CSV, JSON, XLSX, and PDF — with date-range and record-limit filtering.
Visual refresh
Peer, report, and settings screens received a visual refresh to shared UI components. Alongside this, the dark and auto theme options were removed; Studio now uses a single light theme.
Admin and security updates
- Admins can set workspace-level limits on scheduled job concurrency.
- The A2A channel requires a workspace API token for access.
Fixes and reliability improvements
- HTTP tool requests now omit null or undefined fields instead of sending them literally.
- Streaming support added for media analysis inside Flow agent steps.
Action required
Studio and Pulse users do not need to migrate anything manually.
Teams with SharePoint Online content should review the new SharePoint datasource. Teams using OCR-dependent sources should review per-datasource OCR settings, since defaults may differ from prior behavior.
Technical teams that maintain custom apps, SDK integrations, or client-side tools should use the Developer Hub for migration details.