[codex] rename memory extension instructions file

This commit is contained in:
Kevin Liu
2026-04-07 15:22:51 -07:00
parent 3887307f99
commit 3a5c7db657
2 changed files with 6 additions and 6 deletions

View File

@@ -73,7 +73,7 @@ async fn build_consolidation_prompt_points_to_extensions_without_inlining_them()
.await
.unwrap();
tokio_fs::write(
extension_dir.join("instruction.md"),
extension_dir.join("instructions.md"),
"source-specific instructions\n",
)
.await
@@ -91,7 +91,7 @@ async fn build_consolidation_prompt_points_to_extensions_without_inlining_them()
"Memory extensions (under {}/memories_extensions/)",
temp.path().display()
)));
assert!(prompt.contains("<extension_name>/instruction.md"));
assert!(prompt.contains("<extension_name>/instructions.md"));
assert!(!prompt.contains("source-specific instructions"));
assert!(!prompt.contains("source-specific resource"));
}

View File

@@ -36,9 +36,9 @@ Folder structure (under {{ memory_root }}/):
Memory extensions (under {{ memory_extensions_root }}/):
- <extension_name>/instruction.md
- <extension_name>/instructions.md
- Source-specific guidance for interpreting additional memory signals. If an
extension folder exists, you must read its instruction.md to determine how to use this memory
extension folder exists, you must read its instructions.md to determine how to use this memory
source.
If the user has any memory extensions, you MUST read the instructions for each extension to
@@ -150,8 +150,8 @@ Under `{{ memory_root }}/`:
Optional source-specific inputs:
Under `{{ memory_extensions_root }}/`:
- `<extension_name>/instruction.md`
- If extension folders exist, read each instruction.md first and follow it when interpreting
- `<extension_name>/instructions.md`
- If extension folders exist, read each instructions.md first and follow it when interpreting
that extension's memory source.
Mode selection: