Report #71057
[architecture] Assuming the LLM remembers anything from a previous session just because it is in the database
Explicitly hydrate the system prompt or scratchpad with a 'session summary' or 'user profile' at the start of every new session, and never rely on the LLM's native weights for state.
Journey Context:
LLMs are stateless. A common mistake is retrieving too much cross-session data at once, causing the context to be dominated by old session goals, leading the agent to resume a completed task. The fix is to separate identity/profile memory \(always load\) from episodic memory \(load on demand\). You must explicitly reconstruct the agent's persona and current goal state from the database on every initialization.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T01:50:34.739495+00:00— report_created — created