session-history Skill (agentmemory): Past Sessions Timeline
Shows what happened in your recent sessions on this project as a clean timeline, for anyone who asks "what did we do last time".
- Installs
- 14.2K
- on skills.sh
- Stars
- 30.1K
- on GitHub
- Files
- 2
- besides SKILL.md
- Updated
- Oct 2026
- last repo commit
session-history reads the session records that agentmemory keeps and shows them newest first. Each entry has the first 8 characters of the session ID, the project, the start time, the status and the number of observations, with a few highlights such as decisions.
It triggers on questions like "what did we do last time" and "past sessions". Its rule is to show only sessions the tool returned, and an empty history is a real answer. It bundles no scripts and needs the agentmemory server and its MCP tools.
Good for
- Developers picking a project back up after a break
- Anyone who wants a quick overview of past work
- Teams using agentmemory across several agents
Install session-history
Claude Code
- 1
Copy this prompt.
Install the session-history skill in Claude Code. Run this command: npx -y @agentmemory/agentmemory@latest Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js 20 or newer.
This skill only works when the memory server is running and the agentmemory MCP tools are connected. The plugin route is the one the README recommends for Claude Code. The skills-only route installs all 17 skills but does not connect the MCP tools by itself. Pick one route, not both.
From the project README. Source.
What's in the skill
When it loads
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.
Sections in SKILL.md
- Quick start
- Why
- Workflow
- Anti-patterns
- Checklist
- See also
- Troubleshooting
Key facts
- Author
- rohitg00
- Repository
- rohitg00/agentmemory
- Installs on skills.sh
- 14,160 as of 2026-11-02
- GitHub stars
- 30,069 for the whole rohitg00/agentmemory repo
- Last repo commit
- 2026-10-29
What it includes
Slash command that lists recent sessions for this project
The skill file defines no argument hint. Claude lists recent sessions on the project you are in.
Try: “What did we do last time on this project?”
Read ·
session-historyFetches sessions by project, limit, agent and page cursor
Called with the project ID and a limit of 20. If the project ID is unknown it pages through results with nextCursor and matches the working directory. It must never use another project.
Network ·
memory_sessionsNewest first: ID, project, start time and status
Shows the first 8 characters of each session ID. Sessions with observations list their key highlights, as type plus title, and a total count.
Timeline viewShows the title and key decisions when a summary exists
Adds the summary title and decisions for a session when one was recorded.
Read ·
Session summariesSays so when only part of the history is shown
Stops at the requested count or when nextCursor is null, and states when the view is a partial page.
Partial pages
From the official docs
Permissions
Medium risk
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
The plugin records your sessions through hooks
The README lists captured data: user prompts (privacy-filtered), tool name, input and output, errors, and the assistant reply of each turn. Review what is stored in the viewer, and use the forget skill to remove entries. github.com
Installing starts a local server and runs npm code
The setup command pulls the latest package with npx and starts a background server. On macOS and Linux it also needs curl, sh and tar for automatic runtime setup. github.com
Saved memories flow back into later sessions
plugin.json says the plugin injects context into future sessions. In the hook scripts, SessionStart and PreToolUse inject context only when AGENTMEMORY_INJECT_CONTEXT=true, as the README also says. The PreCompact script asks the server for context before each compaction with a default budget of 1500 and prints it as hook output; AGENTMEMORY_PRE_COMPACT_BUDGET=0 turns that off. Our advice: avoid saving text you do not trust, because the assistant reads it back. github.com
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | No read-only switch is documented for these skills. |
|---|---|
| Talks to | The server and viewer bind to loopback (127.0.0.1) by default. Compression or embeddings with a provider you configure use that provider. Local semantic search downloads an embedding model on first use if you set EMBEDDING_PROVIDER=local |
| Sign-in and keys | A local server creates a random secret at ~/.agentmemory/secret with mode 0600 and the bundled clients read it. A remote server needs AGENTMEMORY_SECRET in your environment. |
| Data retention | Memories are stored on your machine in the agentmemory data folder until you delete them. The README says API keys, bearer tokens and <private> tags are stripped before storage. |
| Scopes |
|
Questions
What does the session-history skill do?
It shows your recent sessions on the current project as a timeline: session ID, start time, status, number of observations and a few highlights. It reads data that agentmemory recorded earlier.
How do I install session-history?
Use the install box at the top of this page. Start the agentmemory server first, then add the plugin. The skill calls a tool the server provides, so the folder alone does nothing.
What if I have no past sessions?
Then it shows an empty history. The skill says an empty result is a real answer and it must not invent past work.
How is it different from recap or recall?
The skill file says recap shows the same data grouped by date, handoff jumps into the most recent session, and recall searches all sessions by topic. session-history is the plain list of recent sessions.
Does it need an API key?
The README says keyless mode works without one. Provider keys are only for optional compression or semantic search. A local server makes its own secret.
Is session-history safe?
Its skill file tells Claude to call the memory_sessions tool and list what it returns. The setup around it is larger: the plugin adds hooks that record your sessions and runs a local server. See the safety section on this page.
Information
updated Nov 2, 2026
- Repository
- rohitg00/agentmemory
- Folder
plugin/skills/session-history
Sources
Docs, issue trackers and discussions this page is built from.
Show all 10Hide
- rohitg00/agentmemory README · github.com
- skills CLI commands · github.com
- session-history SKILL.md · github.com
- plugin hooks.json · github.com
- plugin .mcp.json · github.com
- plugin.json · github.com
- Shared TROUBLESHOOTING.md · github.com
- pre-compact.mjs · github.com
- TROUBLESHOOTING.md · github.com
- session-start.mjs · github.com