Summarize recent agent sessions for the current project, grouped by date with highlights from recorded observations. Review today, the last seven days, or a chosen number of sessions, with totals for sessions, days, and observations.
Summarize the last N agent sessions for the current project, grouped by date, with highlight observations per session. Use when the user asks "recap", "what have we been doing", "today", "this week", or wants a rollup of recent work.
Review the instructions the agent will receive before you install.
The user wants a recap. Time window args: $ARGUMENTS
memory_sessions { "project": "<current-project-id>", "limit": 30 }
Then per surviving session: memory_recall { "query": "<top concepts>", "project": "<current-project-id>", "limit": 3 }.
When an agent is requested, pass the same agentId to both calls.
Expected output:
2026-06-07
7f3a9c2 · "Auth refresh rework" · 14 obs · completed
- [8] Rotate refresh tokens on every use
3 sessions across 2 days, 41 observations.
Only summarize sessions and observations the tools returned. An empty window is a real answer, not a prompt to invent activity.
$ARGUMENTS: today = current local date; this week = last 7 days;
last <n> or bare numeric = most recent N; empty = last 10.memory_sessions with the exact recorded project identifier when known
and the requested agentId. Follow nextCursor with the same filters until
the requested window is covered or pages end. When the project identifier is
unknown, match normalized cwd by directory boundary across pages before
applying the time/count window. Sort by startedAt descending.memory_recall, retaining project/agent scope,
and verify each result belongs to that session before including it.WRONG: window is empty, so you summarize "a productive week of auth work" from memory of the conversation.
RIGHT: "No sessions in the last 7 days for this project."
memory_recall, not paraphrase.handoff, session-history, recall: same session data, different lens.See TROUBLESHOOTING.md if memory_sessions or memory_recall is not available.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Connect agentmemory to coding agents such as Claude Code and Codex while preserving existing server settings. It guides configuration, host restarts, and checks that memory tools are available and can save and retrieve information.
Explain how agentmemory stores and retrieves coding agents’ memories, including its engine, search methods, memory lifecycle, ports, and web viewer. Useful for understanding the system or planning extensions to its functions.
Set up and troubleshoot a local agentmemory server by checking MCP connections, authentication, ports, and environment settings. Understand which optional memory features require additional configuration, model downloads, or token usage before enabling them.
Understand how agentmemory automatically records tool activity, prompts, and session boundaries through hooks, actions triggered by session events. Use it to check integration setup, investigate missing records, and distinguish capture from optional summaries and context injection.
Helps agents choose the right agentmemory tool through MCP, a protocol for connecting agents to tools. It explains tool roles and points to parameter references for saving, retrieving, organizing, and maintaining stored knowledge.
Guides HTTP integration with the agentmemory server for saving and searching knowledge. It explains authentication, request conventions, and endpoint references, including how to connect systems that do not support MCP, the agent tool connection protocol.