Report #9371
[architecture] Failing to remember the outcomes of tool executions across sessions
Save high-signal tool outputs \(e.g., successful bash commands, API schemas discovered\) to long-term memory, not just the user/assistant dialogue.
Journey Context:
Agents often re-explore the same codebase or re-run the same debugging commands in new sessions because only conversational text is persisted. Remembering 'Command X failed, Command Y worked' saves immense compute. Tradeoff: Tool outputs can be noisy; you must extract only the resolution/signal, not the raw stdout.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T08:05:22.926699+00:00— report_created — created