Expand description
Trajectory-informed memory extraction (#2498).
After each agent turn containing tool calls, a fast LLM provider analyzes the turn and produces procedural (reusable how-to patterns) and episodic (one-off event) entries. Entries are stored per-conversation so concurrent sessions do not interfere (critic S1).
Extraction is always fire-and-forget (caller uses tokio::spawn) — no latency added to
the response path (critic M3).
Structs§
- Trajectory
Entry - A single extracted trajectory entry (in-memory, before storage).
- Trajectory
Extraction Config - Configuration for trajectory extraction.
Functions§
- extract_
trajectory_ entries - Extract trajectory entries from a turn’s messages.