Search before asking
Description
Follow-up to #876 .
Memory is a core component of agent behavior, but it is currently not observable through the framework’s existing event-based tooling.
Proposal. At each action finish boundary, the framework folds the memory operations performed by that action into generated memory events. These events summarize the net effect per memory scope and operation kind, using a flat dot-key value format.
An agent-run-begin event additionally carries the full short-term memory snapshot at run start, serving as the anchor for offline reconstruction. Event generation is controlled by the memory.generate-event configuration family.
Non-goals. These events do not fully reconstruct long-term memory. LTM events are intended for audit/debug only, because requested updates may differ from the final backend state.
This proposal does not introduce a new persistence format or metrics system. Memory activity reuses the existing event pipeline.
Are you willing to submit a PR?
Search before asking
Description
Follow-up to #876 .
Memory is a core component of agent behavior, but it is currently not observable through the framework’s existing event-based tooling.
Proposal. At each action finish boundary, the framework folds the memory operations performed by that action into generated memory events. These events summarize the net effect per memory scope and operation kind, using a flat dot-key
valueformat.An agent-run-begin event additionally carries the full short-term memory snapshot at run start, serving as the anchor for offline reconstruction. Event generation is controlled by the
memory.generate-eventconfiguration family.Non-goals. These events do not fully reconstruct long-term memory. LTM events are intended for audit/debug only, because requested updates may differ from the final backend state.
This proposal does not introduce a new persistence format or metrics system. Memory activity reuses the existing event pipeline.
Are you willing to submit a PR?