diff --git a/codex-rs/core/templates/memories/read_path.md b/codex-rs/core/templates/memories/read_path.md
index 5f06131fa9..993e04686f 100644
--- a/codex-rs/core/templates/memories/read_path.md
+++ b/codex-rs/core/templates/memories/read_path.md
@@ -1,12 +1,14 @@
 ## Memory
 
-You have access to a memory folder with guidance from prior runs. It can save time and help you stay consistent,
-but it's optional: use it whenever it's likely to help.
+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's likely to help.
 
-Decision boundary: should you use memory for the new user query?
-- You can SKIP memory when the new user query is trivial (e.g. a one-liner change, chit chat, simple formatting, a quick lookup)
-  or clearly unrelated to this workspace / prior runs / memory summary below.
-- You SHOULD do a quick memory pass when the new user query is ambiguous and relevant to the memory summary below, or when consistency with prior decisions/conventions matters.
+Decision boundary: should you use memory for a new user query?
+- You may skip memory when the new query is trivial (e.g., a one-line change, chit-chat,
+simple formatting) or clearly unrelated to this workspace or the memory summary below.
+- You SHOULD do a quick memory pass when the new query is ambiguous and likely relevant to
+the memory summary below, or when consistency with prior decisions/conventions matters.
+Especially if the user asks about a specific repo/module/code path that seems relevant,
+skim/search the relevant memory files first before diving into the repo.
 
 Memory layout (general -> specific):
 - {{ base_path }}/memory_summary.md (already provided below; do NOT open again)
@@ -25,12 +27,14 @@ Quick memory pass (when applicable):
 4) If nothing relevant turns up, proceed normally without memory.
 
 During execution: if you hit repeated errors, confusing behavior, or you suspect there's relevant prior context,
-it's worth redoing the quick memory pass. Treat memory as guidance, not truth: if memory conflicts with the current repo state,
-tool outputs, or environment, user feedback, the current state wins. If you discover stale or misleading guidance, update the
-memory files accordingly.
+it's worth redoing the quick memory pass. 
+
+When to update memory:
+- Treat memory as guidance, not truth: if memory conflicts with the current repo state, tool outputs, or environment, user feedback, the current state wins. If you discover stale or misleading guidance, update the memory files accordingly.
+- When user explicitly asks you to update the memory, you should revise the files accordingly.
 
 ========= MEMORY_SUMMARY BEGINS =========
 {{ memory_summary }}
 ========= MEMORY_SUMMARY ENDS =========
 
-If memory is relevant for a new user query, start with the quick memory pass above.
+If memory seems to be relevant for a new user query, always start with the quick memory pass above.