Sandbox Interruption and Execution Budgets
Microsoft updated the Hyperlight integration in Agent Framework python-1.26.0 to curb runaway tasks. Guest code runs now enforce a default 30-second budget and halt immediately upon caller cancellation. Operators can increase this duration through tool settings when workloads legitimately need more time.
The release notes state that the cancellation mechanism depends on Sandbox.interrupt_handle, which is documented for Hyperlight SDK 0.9.0 and later. Although installation permits version 0.8.0, older packages lack an interruption fallback. Host callbacks and runtime startup also operate outside these guest interruption controls.
Approval Isolation and Replay Policy Boundaries
The framework addresses multi-agent boundary confusion by isolating run-level tool approvals when an agent operates as a tool. In declarative bindings, registered approval policies, call counters, and result parsing metadata remain intact during invocation.
For session replay and message history, Core and model-specific adapters bind FIDES policy enforcement directly to effective service continuations. Systems require complete local history coverage and reject altered, opaque, or partially archived continuations prior to tool approvals or model dispatch. When service-owned history is missing, the system fails closed.
Integration Baselines and Memory Deprecations
The GitHub Copilot integration now requires Copilot CLI version 1.0.85 or later and refuses to start if older versions are detected. Additionally, Microsoft marked five experimental memory storage APIs for removal after December 31, 2026. Teams must transition to FileMemoryProvider and AgentFileStore, which use distinct directory layouts and do not migrate legacy records automatically.
Our assessment
Teams building nested agents should check if subagents inherited approval decisions unintentionally under earlier releases. The 30-second Hyperlight budget creates a hard wall for slow code tasks, making it critical to review execution limits alongside SDK versions. Because the file memory replacement does not migrate data or persist transcript history by default, memory migrations will require custom export scripts.
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.





