Child state cannot be a checkpoint footnote
Microsoft Agent Framework has fixed a recovery gap in nested Python workflows: a parent checkpoint can now carry the child workflow’s own state, rather than resuming with only a remembered request.
More From This Edition
All editions ›OpenWorker takes the agent loop out of the IDE
Mastra: turning TypeScript application primitives into agent infrastructure
API Discovery: Let one model ask another before it answers
Recent Editions
Full history ›The Approval Prompt Needs To Name the Tool That Asked
Codex’s command-approval chain used to lose the plugin that initiated a command; a new change keeps that attribution through review, history, completion, and denial because consent without a requester is weak consent.
The 67,000-Star Repo That Changed What It Was
Open Interpreter’s GitHub audience remembers a Python computer agent. The code behind the same counter is now a Rust fork of Codex—and almost all of the stars arrived before that switch.
An Agent's Sign-In Link Is Not a Timeout
OpenWork's newest MCP work carries a provider's structured authorization link through a failed tool call, so the person who owns the account can act instead of watching an agent retry the wrong problem.
The Diff Can't Be Guesswork Once an Agent Writes
OpenClaw is making a simple rule explicit: when an agent writes a file, a review surface should show the patch it can prove—and show uncertainty when it cannot.
How AI Agents Work
The long-form map behind the daily paper: context, tools, loops, memory, delegation, safety, interface, and trust.