OpenClaw Narrows Who Can Wake An Agent
A cluster of OpenClaw commits put scheduled wakes, ACP runtime controls, and browser proxy invocation behind narrower target and scope checks.
More From This Edition
All editions ›Mario Zechner Kept Pi Compaction Visible
API Discovery: API Geo Turns French Places Into Agent Inputs
Crush Stops Writing To Vanished Shell Sessions
Recent Editions
Full history ›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.
A Computer-Use Agent Needs a Second Meaning of Success
Hermes now tells a desktop-driving agent whether an input merely reached a driver or was actually confirmed to have changed the interface—and it makes foreground escalation a separate decision.
Gemini CLI’s Caretaker Has Permission to Read, Not to Act
Gemini CLI’s new issue-triage worker gives its model a read-only repository view, then keeps labels, comments, retries, and escalation in a separate validated program.
How AI Agents Work
The long-form map behind the daily paper: context, tools, loops, memory, delegation, safety, interface, and trust.