clone/codex
1
0
Fork 0
mirror of https://github.com/openai/codex.git synced 2026-04-24 14:45:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix prompt

Browse Source
This commit is contained in:
jif-oai
2026-02-24 14:04:32 +00:00
parent ac01d171f5
commit 1fa24419ad
1 changed files with 13 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
codex-rs/core/templates/memories/read_path.md
View File

@@ -55,20 +55,22 @@ When to update memory:
Memory citation requirements:
- If ANY relevant memory files were used: append exactly one
`<memory_citation>` block as the VERY LAST content of the final reply.
`<oai-mem-citation>` block as the VERY LAST content of the final reply.
Normal responses should include the answer first, then append the
`<memory_citation>` block at the end.
`<oai-mem-citation>` block at the end.
- Use this exact structure for programmatic parsing:
<memory_citation>
```
<oai-mem-citation>
<citation_entries>
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]
</citation_entries>
<thread_ids>
<rollout_ids>
019c6e27-e55b-73d1-87d8-4e01f1f75043
019c7714-3b77-74d1-9866-e1f484aae2ab
</thread_ids>
</memory_citation>
</rollout_ids>
</oai-mem-citation>
```
- `citation_entries` is for rendering:
- one citation entry per line
- format: `<file>:<line_start>-<line_end>|note=[<how memory was used>]`
@@ -80,13 +82,13 @@ rollout_summaries/2026-02-17T21-23-02-LN3m-weekly_memory_report_pivot_from_git_h
- list entries in order of importance (most important first)
- `note` should be short, single-line, and use simple characters only (avoid
unusual symbols, no newlines)
- `thread_ids` is for us to track what previous rollouts you find useful:
- include one thread id per line
- thread ids should look like UUIDs (for example,
- `rollout_ids` is for us to track what previous rollouts you find useful:
- include one rollout id per line
- rollout ids should look like UUIDs (for example,
`019c6e27-e55b-73d1-87d8-4e01f1f75043`)
- include unique ids only; do not repeat ids
- an empty `<thread_ids>` section is allowed if no thread ids are available
- you can find thread ids in rollout summary files and MEMORY.md
- an empty `<rollout_ids>` section is allowed if no rollout ids are available
- you can find rollout ids in rollout summary files and MEMORY.md
- do not include file paths or notes in this section
- Never include memory citations inside pull-request messages.
- Never cite blank lines; double-check ranges.