memory: never forget without explicit user instruction
This commit is contained in:
parent
1b73b22064
commit
16ae3e1308
|
|
@ -19,7 +19,8 @@ call_tool: calls=[{tool: "memory_remember", args: ["<title>", "<tags_csv>", "<bo
|
|||
**Constraints**:
|
||||
- One memory per distinct fact.
|
||||
- Before writing, recall on the same topic to avoid duplicates. If a closely related memory exists, update it rather than creating a new one.
|
||||
- Do not store stale facts. If you learn that a previously stored fact is wrong or outdated, update or replace it.
|
||||
- Do not store stale facts. If you learn that a previously stored fact is wrong or outdated, update it.
|
||||
- Never delete (forget) a memory without explicit user instruction.
|
||||
- There is no length limit on memory bodies. Store as much detail as needed for the fact to be useful in a future session.
|
||||
- **Act autonomously.** Do not ask the user whether to remember something — if the trigger condition is met, remember it.
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ while IFS= read -r file; do
|
|||
now=$(date +%s)
|
||||
age_days=$(( (now - mtime) / 86400 ))
|
||||
if [ $age_days -ge $stale_days ]; then
|
||||
status="STALE (${age_days}d — verify or forget)"
|
||||
status="STALE (${age_days}d — verify)"
|
||||
else
|
||||
status="fresh"
|
||||
fi
|
||||
|
|
|
|||
Loading…
Reference in New Issue