From 3f2b7ede0b1b7d9dfc317bd02f15eeed26ed8d72 Mon Sep 17 00:00:00 2001 From: jif-oai Date: Mon, 18 May 2026 19:25:27 +0200 Subject: [PATCH] nit: read prompt (#23332) --- .../memories/read/templates/memories/read_path.md | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/codex-rs/memories/read/templates/memories/read_path.md b/codex-rs/memories/read/templates/memories/read_path.md index 828b30923e..00639c7e8c 100644 --- a/codex-rs/memories/read/templates/memories/read_path.md +++ b/codex-rs/memories/read/templates/memories/read_path.md @@ -25,7 +25,7 @@ Memory layout (general -> specific): - scripts/ (optional helper scripts) - examples/ (optional example outputs) - templates/ (optional templates) - - {{ base_path }}/rollout_summaries/ (per-rollout recaps + evidence snippets) +- {{ base_path }}/rollout_summaries/ (per-rollout recaps + evidence snippets) - The paths of these entries can be found in {{ base_path }}/MEMORY.md or {{ base_path }}/rollout_summaries/ as `rollout_path` - These files are append-only `jsonl`: `session_meta.payload.id` identifies the session, `turn_context` marks turn boundaries, `event_msg` is the lightweight status stream, and `response_item` contains actual messages, tool calls, and tool outputs. - For efficient lookup, prefer matching the filename suffix or `session_meta.payload.id`; avoid broad full-content scans unless needed. @@ -57,9 +57,6 @@ How to decide whether to verify memory: disruptive, it is acceptable to answer from memory in an interactive turn, but you should say that it is memory-derived, note that it may be stale, and consider offering to refresh it live. -- If a fact is lower-drift and cheap to verify, use judgment: verification is - more important when the fact is central to the answer or especially easy to - confirm. - If a fact is lower-drift and expensive to verify, it is usually fine to answer from memory directly. @@ -72,10 +69,8 @@ When answering from memory without current verification: - If live verification was skipped and a refresh would be useful in the interactive context, consider offering to verify or refresh it live. - Do not present unverified memory-derived facts as confirmed-current. -- For interactive requests, prefer a short refresh offer over silently doing - expensive verification that the user did not ask for. -- When the unverified fact is about prior results, commands, timing, or an - older snapshot, a concrete refresh offer can be especially helpful. +- Prefer a short refresh offer for interactive questions, especially about prior + results, commands, timing, or older snapshots. Memory citation requirements: @@ -88,7 +83,7 @@ Memory citation requirements: MEMORY.md:234-236|note=[responsesapi citation extraction code pointer] -rollout_summaries/2026-02-17T21-23-02-LN3m-weekly_memory_report_pivot_from_git_history.md:10-12|note=[weekly report format] +rollout_summaries/2026-02-17T21-23-02-LN3m-example.md:10-12|note=[weekly report format] 019c6e27-e55b-73d1-87d8-4e01f1f75043