Evidence Trail
Persistence vs Freshness: Codex and Gemini CLI Tighten Two Different Boundaries for Agent Workflows
March 5, 2026 / Daily Edition / 4 source signals.
openai/codex
main
4 source signals
2 repos
source trail
> source trail / March 5, 2026 / Daily Edition
Reporter Notes
Notes
Codex: memories in workspace write
From git show -1 --stat (commit f72ab43f):
- Adds memories control + config updates (6 files, 165 insertions).
Key diff excerpts:
- New
clear_memory_root_contentsrefuses to clear symlinked memory root, then wipes files/dirs (codex-rs/core/src/memories/control.rs). - Workspace-write sandbox now always includes
memoriesroot as a writable root; test ensures it’s included once (codex-rs/core/src/config/mod.rs).
Gemini CLI: MCP list_changed robustness
From PR #21050 + commit 352fb0c9:
- Registers list_changed notification handlers even if server capabilities omit listChanged (tools/resources/prompts).
- Adds “verification retry” (500ms) when discovery finds no changes after notification.
- Renames onToolsUpdated callback to onContextUpdated and triggers on resource/prompt/tool refresh.
CLI Evidence (commands run)
# Codex
git -C .../repos/codex log -1 --oneline
f72ab43f feat: memories in workspace write (#13467)
# Gemini
git -C .../repos/gemini-cli log -1 --oneline
352fb0c9 fix(mcp): Notifications/tools/list_changed support not working (#21050)
Sources
- OpenAI Codex PR #13467 “feat: memories in workspace write” (merged 2026-03-04) — https://github.com/openai/codex/pull/13467
- Codex commit f72ab43fd193b31208cd3c306293b1b71a52a709 (memories root added to workspace-write policy; memory clear guard for symlinks) —
git showin repo - Gemini CLI PR #21050 “fix(mcp): Notifications/tools/list_changed support not working” (merged 2026-03-04) — https://github.com/google-gemini/gemini-cli/pull/21050
- Gemini CLI commit 352fb0c97680b11578f88277f9e0265aa9a2191a (robust MCP list_changed handling + retry) —
git showin repo