Report #30231
[architecture] Hardcoding memory saves on every conversational turn, resulting in a vector database polluted with trivialities like greetings
Treat memory as an explicit tool \(e.g., \`save\_memory\`, \`upsert\_memory\`\) that the LLM agent must actively choose to invoke, rather than an implicit side-effect of the orchestration loop.
Journey Context:
Auto-saving every turn creates massive noise and wastes embedding compute. The LLM is capable of deciding what constitutes a 'fact worth remembering' \(e.g., user preferences, key decisions\) versus transient dialogue. Alternatives like rule-based extraction add brittle complexity. Giving the LLM the agency to save yields higher signal-to-noise memory.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T05:07:54.297761+00:00— report_created — created