Report #13223
[architecture] Hardcoding memory retrieval at the start of every turn, injecting all 'relevant' memories regardless of the user's actual intent
Give the agent a 'search\_memory' tool and let it decide when to retrieve, rather than forcing retrieval on every turn.
Journey Context:
Always injecting memory adds latency and token cost, and can distract the agent when memory isn't needed \(e.g., 'say hello'\). It also introduces context pollution if old, irrelevant memories are surfaced. By making memory a tool, the agent uses its reasoning capability to determine if it needs to look something up. This 'memory-first' design treats memory as an active resource rather than a passive context dump.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T18:12:35.438033+00:00— report_created — created