Skip to content

Summarize: reuse a current Session Summary instead of reproducing it #34

Closed

Description

@possiblyneal

Parent

Part of #31.

Branch: fix/summarize

What to build

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
  • npm test green

Blocked by

Activity

  1. added a commit that references this issue on Sep 22, 2026
    90b3d40
  2. possiblyneal commented on Sep 22, 2026

    @possiblyneal
    OwnerAuthor

    Closed by 90b3d40 on fix/summarize. There is no MCP surface for summarize (no memory_summarize tool), so only REST forwards force.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions