From d724ceb5214a9817d1362b2a5b7da508f161c421 Mon Sep 17 00:00:00 2001 From: chaithanyak42 Date: Thu, 26 Mar 2026 15:12:29 +0530 Subject: [PATCH] fix(openclaw): prevent extraction of standalone timestamps as memories The extraction LLM was storing "User indicates current time is X" as durable memories every time OpenClaw injected timestamp context into messages. noah48 alone accumulated 10K+ timestamp memories. Add explicit exclude rule: timestamps as standalone facts are never worth storing, but timestamps anchoring real facts ("User installed Ollama on 2026-03-21") should still be preserved. Co-Authored-By: Claude Opus 4.6 (1M context) --- openclaw/config.ts | 1 + 1 file changed, 1 insertion(+) diff --git a/openclaw/config.ts b/openclaw/config.ts index f564f237a..e0da5a6cd 100644 --- a/openclaw/config.ts +++ b/openclaw/config.ts @@ -117,6 +117,7 @@ Exclude (NEVER store): - Transient UI/navigation states ("user is in the admin panel", "relay is attached") - Ephemeral process status ("download at 50%", "daemon not running", "still syncing") - Cron heartbeat outputs, NO_REPLY responses, compaction flush directives +- The current date/time as a standalone fact — timestamps are conversation context, not durable knowledge. "User indicates current time is 3:25 PM" is NEVER worth storing. However, DO use timestamps to anchor other facts: "User installed Ollama on 2026-03-21" is correct. - System routing metadata (message IDs, sender IDs, channel routing info) - Generic small talk with no informational content - Raw code snippets (capture the intent/decision, not the code itself)