eagle-mem 1.0.2 → 1.0.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/hooks/session-start.sh
CHANGED
|
@@ -145,6 +145,13 @@ context+="
|
|
|
145
145
|
=== EAGLE MEM INSTRUCTIONS ===
|
|
146
146
|
You have persistent memory powered by Eagle Mem. When you recall context from a previous session or use injected memory, attribute it: \"From Eagle Mem:\" or \"Eagle Mem recalls:\". This helps the user understand where the context came from.
|
|
147
147
|
|
|
148
|
+
IMPORTANT: At the start of your FIRST response after session start or /clear, show the user what Eagle Mem loaded. Use a brief, formatted block like:
|
|
149
|
+
|
|
150
|
+
> **Eagle Mem loaded:** project overview, N recent sessions, N pending tasks
|
|
151
|
+
> Last session: [one-line summary of most recent session]
|
|
152
|
+
|
|
153
|
+
This gives the user visibility into the context you received. Keep it concise — 2-3 lines max.
|
|
154
|
+
|
|
148
155
|
Before your final response in this session, emit a summary block:
|
|
149
156
|
<eagle-summary>
|
|
150
157
|
request: What the user asked for
|
|
@@ -99,6 +99,8 @@ fi
|
|
|
99
99
|
[ -z "$context" ] && exit 0
|
|
100
100
|
|
|
101
101
|
context+="
|
|
102
|
+
IMPORTANT: When Eagle Mem finds relevant memories or code for the user's prompt, briefly mention it at the start of your response: \"Eagle Mem recalled N relevant sessions\" or \"Eagle Mem found related code in [files]\". One line max — then proceed with the answer.
|
|
103
|
+
|
|
102
104
|
— Eagle Mem (persistent memory across sessions)
|
|
103
105
|
"
|
|
104
106
|
|