Shows recent work sessions for the current project as a timeline, newest first. It includes session identifiers, start times, status, recorded observation counts, and available highlights or decisions, using only history returned by the memory tool.
Show what happened in recent past sessions on this project as a clean timeline. Use when the user asks "what did we do last time", "session history", "past sessions", or wants an overview of previous work.
Review the instructions the agent will receive before you install.
The user wants an overview of recent sessions on this project.
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-IP
Only show sessions and observations the tool returned. An empty history is a real answer, never a cue to invent past work.
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.nextCursor. State when the displayed history is a partial page. Present in
reverse chronological order: session id (first 8), project, start
time, status.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.
recap: same data grouped by date with highlights.handoff: jump straight into the most recent session.recall: search across all sessions by topic.See TROUBLESHOOTING.md if memory_sessions 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.