July 2026 Release
July 2026 was the largest product month of the year so far. Agent Ops was rearchitected around a persistent, per-project sandbox, and its capabilities — projects, tasks, sandboxes, and reusable skills — were unified with Flows into a single Flow Projects model. A Microsoft Teams channel also shipped, and SharePoint connectivity continued to be hardened.
Developers maintaining custom applications should use the Developer Hub for API, SDK, package, and migration notes.
Highlights
- Flows and Agent Ops are unified under Flow Projects: one project now owns secrets, sandboxes, memory, and tasks.
- Agent sandboxes gained browser automation, persistent memory, package installs, and human-in-the-loop notifications.
- Flow Copilot gained persistent chat sessions and clearer run inspection.
- New Microsoft Teams channel.
- Flow credit billing is now calculated exactly rather than approximated.
New in Studio
Flow Projects
Flows can now be organized into Projects. A project is a shared workspace that owns the resources a single flow cannot own on its own:
- Secrets — credentials shared across the project's flows and sandboxes.
- Sandboxes — persistent machines that flow steps and agents can run commands and code in.
- Memory — project- or flow-scoped state that persists across runs.
- Tasks — a queue of work items people hand to the project's flows, with statuses and human approval where needed.
New Smart Agent and Subflow steps bring agent capability directly into a flow, and Skills — reusable playbooks — can be attached to an agent so it only loads the ones it needs for a given task.
This is where the automation capability previously delivered as a separate Agent Ops area now lives. See Projects & Flows, Tasks, Sandboxes, and Skills.
Expanded sandbox capabilities
Project sandboxes gained a wider set of capabilities this month, including browser automation for tasks that need to navigate and read web pages, persistent memory that improves over repeated runs, gated package installs, and human-in-the-loop notifications (including email) for work that needs a person's input before continuing. Git push actions from a sandbox now require project-level approval.
Flow Copilot
Flow Copilot — the assistant that helps build and edit flows — now keeps persistent chat sessions per project, and shares a unified run timeline between the debug panel and the runs view for easier inspection.
Microsoft Teams channel
A Peer can now be connected to Microsoft Teams, using a per-app bot identity so each Peer appears as its own chat target in Teams.
See Microsoft Teams.
Flow credit billing
Flow runs are now billed on exact, per-model usage rather than an approximation.
Other updates
- Continued work on SharePoint connectivity, including an OAuth-based connection flow and an admin-consent step; this was still being refined through the month.
- Further visual design alignment across Studio's shared UI components.
- New model options were added.
Fixes and reliability improvements
- Scanned PDF handling improved, with a clearer fallback when OCR isn't configured.
- Portal chat attachment download fixes.
Action required
Studio and Pulse users do not need to migrate anything manually.
Teams that were using Agent Ops as a separate area should note that its capabilities now live under Flow Projects — existing automations continue to work, organized as projects.
Technical teams that maintain custom apps, SDK integrations, or client-side tools should use the Developer Hub for migration details.