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
In-process memory_sessions ignores limit and returns Sessions unsorted #49
The in-process MCP tool memory_sessions should return the same newest-first page that GET /agentmemory/sessions returns: sorted by startedAt (rows without one last), honouring limit, with total. Today it reads the sessions scope directly, ignores limit, and returns rows in insertion order, so the recap, handoff and session-history skills get the oldest Sessions when they run against the in-process server instead of the standalone shim.
Acceptance criteria
memory_sessions with limit: N returns the N newest Sessions and a total
A Session row without startedAt never throws and sorts last
Test at the MCP handler seam, hand-rolled mockKV()/mockSdk()
Activity
possiblyneal commentedon Oct 6, 2026
Fixed on branch
possiblyneal/wolffish(ba4bee7). SharedlistSessionsPageinsrc/functions/sessions-page.tsbacks both REST and MCP.Merge #49 memory_sessions page