Report #60061
[architecture] Agent overwrites critical long-term memory with temporary task-specific state when switching contexts
Isolate working memory \(scratchpad for current task\) from long-term memory \(core knowledge base\). Only commit validated results from the scratchpad to long-term memory upon task completion.
Journey Context:
Agents often use a single memory store for both their scratchpad \(e.g., 'I am currently trying to parse file X, attempt 3'\) and core facts \(e.g., 'The database port is 5432'\). If a task fails or the agent switches contexts, the scratchpad state can pollute or overwrite stable facts. By explicitly separating volatile working memory \(cleared on task reset\) from persistent long-term memory \(updated only on successful task completion or reflection\), the agent prevents transient errors from corrupting its core knowledge.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T07:18:14.228108+00:00— report_created — created