Codex Stops a Thread’s Permission From Leaking Into a Read-Only Environment
A new Codex regression test makes the sharpest promise in its permissions work: a selected environment configured read-only must stay read-only even when the surrounding thread can write.
More From This Edition
All editions ›Recent Editions
Full history ›An Agent’s ‘No’ Needs a Way Back—But Not a Shortcut
Qwen Code now offers one manual review only for the exact action its AUTO mode blocked—turning a false positive into an accountable decision instead of a workaround hunt.
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.
How AI Agents Work
The long-form map behind the daily paper: context, tools, loops, memory, delegation, safety, interface, and trust.