A Restricted Workspace Should Not Start Its Own Tools
Gemini CLI now gives an explicitly restricted or untrusted workspace a narrower configuration path: repository-defined tools, MCP servers, policies and telemetry no longer accompany its A2A server into startup.
More From This Edition
All editions ›Recent Editions
Full history ›No Mail Server Is Not a Free Pass
QM’s new admin-login route lets an already authorized administrator open a portal before outbound email exists—but only through a five-minute, origin-bound, one-use handoff that gets checked again at the door.
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.
How AI Agents Work
The long-form map behind the daily paper: context, tools, loops, memory, delegation, safety, interface, and trust.