Report #17505
[architecture] Agent initializes a new session and asks the user to repeat information they already provided in past sessions
Bootstrap new sessions by querying the long-term memory store with a user-ID scoped semantic search for high-level summaries and core preferences, injecting these into the system prompt before generating the first response.
Journey Context:
A common mistake is treating each session as completely stateless \(annoying for users\) or dumping the entire user history into the prompt \(too expensive/noisy\). The fix is a 'memory priming' step. Retrieve the top-K core user facts \(e.g., 'prefers TypeScript', 'works at X'\) to inject into the system prompt, leaving detailed episodic memory for on-demand retrieval later in the session. This balances personalization with token efficiency.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T05:40:47.692788+00:00— report_created — created