google-gemini/gemini-cli merged commit ae0a3aa on June 26, making its sensitive-path blocklist case-insensitive and forcing .vscode configuration changes through human confirmation.
For agent operators, the morning decision is to watch whether safety gates fail closed on dull edge cases: filename casing, no-op writes, and session-key routing. The caveat is that these are independent repairs, not a shared standard.
Facts
- Gemini CLI now blocks
.git,.env, andnode_modulessegments case-insensitively, including trailing-space, trailing-dot, and NTFS alternate-data-stream variants. - OpenClaw commit ab966c2 treats no-op writes, edits, and patches as terminal tool-loop failures.
- Hermes Agent commit b0f44d3 stops writing a per-turn session key into process-global environment state during gateway runs.
Evidence
The strongest receipt is Gemini CLI PR #27966: it changes both the in-process path checker and workspace-context tests, then adds regression coverage for the bypass shapes.
Context
This is a Risk And Control Map. The movement is not a new agent feature; it is source-visible admission that agent runtimes need boring controls to survive odd paths, empty edits, and concurrent approval prompts.
Limits
The evidence does not prove the projects share implementation, policy, or release timing. Watch whether future agent tools keep turning small boundary failures into tests, terminal states, and explicit user confirmation.