Protocol migration and client lifecycles
Microsoft rolled out python-1.23.0 for its Agent Framework, introducing a foundational transition to Model Context Protocol 2.x. The release migrates transports, schemas, error formats, and lifecycle handling across core and hosting components. Alongside the protocol update, the framework now differentiates between caller-owned and framework-owned client lifecycles, establishing predictable teardown rules across workflows and testing user interfaces.
Agent interactions also receive finer metadata forwarding controls. The framework allows allowlisted passing of function invocations and client arguments directly from agent-to-agent request metadata, reducing ad hoc protocol plumbing between interconnected runtimes.
Tighter execution boundaries and authorization
The release enforces several breaking boundaries designed to prevent accidental exposure and unvetted container commands. Endpoint registration for AG-UI now mandates either an explicit authorization scope or a formal single-user declaration before accepting traffic. In addition, the Docker execution wrapper renames its extra runtime arguments option to clarify that unvalidated parameters require explicit trust.
Local execution security extends to shell sandboxes as well. Stateless shell tools can no longer inherit standard input streams from the host system, cutting off a potential vector for silent input leaks during local tool runs.
Provider fallbacks and atomic state updates
Core orchestration adds an opt-in trailing user turn to handle external model providers that emit empty text responses after assistant-concluding prompts. Core execution updates also make state modifications to Memory and Todo components atomic while isolating task contexts across connected tool calls.
Our assessment
Teams building on Microsoft Agent Framework should audit their deployment configurations before upgrading. Workflows relying on AG-UI interfaces need explicit scope registrations to avoid service startup failures. Developers managing containerized tool sandboxes must update Docker argument flags and verify that command pipelines do not depend on inherited host input. Finally, projects utilizing external tool servers should test client lifecycle handling against the updated MCP 2.x transport definitions.
Source: Microsoft original publication.
Read the original material
Microsoft (opens in a new tab)The article date belongs to Agentic Horizon. The source publication date is listed separately. Vendor claims remain attributed; we have not independently tested the reported capability.
