You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: prompts/en/memory_persistence.md.j2
+21-2Lines changed: 21 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -28,9 +28,17 @@ This is an automatic process triggered periodically during conversation. You are
28
28
- Use `part_of` when a detail belongs to a larger concept already in memory
29
29
30
30
4. **Extract events.** While reviewing the conversation, identify key decisions, important events, and errors. Include them in the `events` field of `memory_persistence_complete`:
31
-
- `event_type`: "decision" for commitments or choices made, "error" for failures or problems, "system" for other notable events
31
+
- `event_type`:
32
+
- `"decision"` for commitments or choices made
33
+
- `"user_correction"` when the user corrects a prior assumption, instruction, or framing
34
+
- `"decision_revised"` when a prior choice changes after feedback or new information
35
+
- `"error"` for failures or problems
36
+
- `"system"` for other notable events
32
37
- `summary`: one-line description of what happened
33
-
- `importance`: 0.0-1.0 score (decisions and errors typically 0.6-0.8)
38
+
- Normalize relative time references to absolute dates/times with timezone
39
+
(for example `2026-03-31T14:20:00-04:00`) so downstream memory checks are
40
+
stable across sessions.
41
+
- `importance`: 0.0-1.0 score (`decision`, `user_correction`, and `decision_revised` are typically 0.6-0.8)
34
42
- Events feed the agent's temporal working memory — they help the agent remember *what happened today*, not just facts.
35
43
36
44
5. **Finish with the terminal tool.** You must call `memory_persistence_complete` before finishing:
@@ -46,3 +54,14 @@ This is an automatic process triggered periodically during conversation. You are
46
54
4. Focus on the most recent portion of the conversation — older content has likely already been captured by previous persistence runs.
47
55
5. Do not invent memory IDs. Every ID in `saved_memory_ids` must come from a real successful `memory_save` call in this run.
48
56
6. Do not return plain text as the terminal result. End the run by calling `memory_persistence_complete`.
57
+
58
+
7. Exclude non-durable information:
59
+
- Raw repo-state or derivable state such as `ls`, `pwd`, environment output,
60
+
git status/history, or full file diffs unless it materially changes the
Save a memory to long-term storage. Memories persist across conversations and can be recalled later via branches.
1
+
Save a validated, durable memory to long-term storage. Use this only for information that should persist across conversations and be recalled later via branches.
0 commit comments