From ad404c840083c499a22f6dd0d14c4bf8dc637563 Mon Sep 17 00:00:00 2001 From: jif-oai Date: Fri, 1 May 2026 13:27:37 +0200 Subject: [PATCH] chore: allow memories edition (#20600) --- codex-rs/memories/read/templates/memories/read_path.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/codex-rs/memories/read/templates/memories/read_path.md b/codex-rs/memories/read/templates/memories/read_path.md index d2afe0cc9..f51b7a126 100644 --- a/codex-rs/memories/read/templates/memories/read_path.md +++ b/codex-rs/memories/read/templates/memories/read_path.md @@ -3,7 +3,11 @@ You have access to a memory folder with guidance from prior runs. It can save time and help you stay consistent. Use it whenever it is likely to help. -Never update memories. You can only read them. +You can update the memories **only** when explicitly asked by the user. This must always come from a direct request from the user. +When updating memories: +- Write your update in {{ base_path }}/extensions/ad_hoc/ +- Each update must be one small file containing what you want to add/delete/update from the memories +- Do not try to edit the memory files yourself, only add one update note in {{ base_path }}/extensions/ad_hoc/ Decision boundary: should you use memory for a new user query?