按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。
The user wants an overview of recent sessions on this project.
Quick start
memory_sessions { "project": "<current-project-id>", "limit": 20 }Expected output:
7f3a9c2 · app · 2026-06-07 09:00 · completed · 14 obs
- decision: Rotate refresh tokens on every use
b21d004 · app · 2026-06-05 14:00 · completed · 9 obs
- code: limit.ts counts per-IPWhy
Only show sessions and observations the tool returned. An empty history is a real answer, never a cue to invent past work.
Workflow
- Use the exact project identifier recorded by the host and pass it to
memory_sessions, with agentId when requested. If it is unknown, page through sessions using nextCursor and match normalized cwd by directory boundary before choosing the most recent 20. Never substitute another project.
- Preserve scope filters on every page; stop at the requested count or a null
nextCursor. State when the displayed history is a partial page. Present in reverse chronological order: session id (first 8), project, start time, status.
- For sessions with observations, show the key highlights (type plus title).
- Note the total observation count per session.
- When a session summary exists, surface its title and the key decisions.
Anti-patterns
WRONG: the tool returns two sessions, you describe "several sessions of steady progress" and add ones you remember from the conversation.
RIGHT: show exactly the two sessions returned, each with its real id, status, and observation count.
Checklist
- Every session shown came from the tool response.
- Project/directory scope was checked before selecting the displayed window.
- Order is reverse-chronological.
- Per-session observation counts match the response.
- No session or highlight was invented or merged.
See also
recap: same data grouped by date with highlights.handoff: jump straight into the most recent session.recall: search across all sessions by topic.
Troubleshooting
See TROUBLESHOOTING.md if memory_sessions is not available.

