You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Summarize: reuse a current Session Summary instead of reproducing it #34
Stopping a Session that already has a current Session Summary returns it without calling the LLM. A Session Summary is current when no Observation arrived after it was written; Observations are append-only within a Session, so the check compares the summary's recorded Observation count to the Session's current count. An explicit force input bypasses reuse. No give-up rule is added for Sessions that keep failing.
Acceptance criteria
With a stored summary whose Observation count matches, mem::summarize returns it and the provider is never called
With Observations added since, the provider is called and the new summary replaces the old
force: true calls the provider even when the summary is current
The REST and MCP surfaces that reach mem::summarize accept and forward force
Activity
fix(summarize): reuse a current Session Summary instead of reproducin…
possiblyneal commentedon Sep 22, 2026
Closed by 90b3d40 on fix/summarize. There is no MCP surface for summarize (no memory_summarize tool), so only REST forwards force.