The Last Click Shouldn’t Redirect an Automation
OpenWork has stopped a scheduled Automation from silently following whichever workspace a person activated last; a job can now carry its intended place with it.
More From This Edition
All editions ›The Swarm Was a Systems Bug Before It Was a Civilization
Codex Says It Stopped Wasting Your Allowance. The Public Code Can Prove Only Part of It
API Discovery: Tool Calls Need a Home in the Stream
Recent Editions
Full history ›Hermes Decides That a Preference Can Have a Home
Hermes is redrawing a deceptively important line: a correction learned while doing one task belongs with that task's skill, while persistent memory is for facts that should matter everywhere.
Before Codex Trusts a Workspace, It Stops Letting the Workspace Choose Its Helpers
A merged Codex change moves automatic pre-trust helper lookups to known system locations, sanitizes plugin-sync Git, and makes diagnostics inspect a workspace-influenced path without running what they find.
A Child Agent’s Approval Request Shouldn’t Hide in Another Tab
Openwork now brings a child session’s blocked permission into the parent task; fresh Goose state-machine work shows why seeing the ask is only half the control.
A Completed Agent Run Is Not a Successful One
OpenHands now treats a finished process and a successful task as different facts—so an automation can be completed, blocked, and operationally failing at the same time.
How AI Agents Work
The long-form map behind the daily paper: context, tools, loops, memory, delegation, safety, interface, and trust.