SkillHub

Skills rohitg00 agentmemory agentmemory

session-history

Use it when:
You ask "what did we do last time" or want an overview of past sessions on this project.
It does:
Fetches the project's 20 most recent sessions from agentmemory, newest first.
You get:
A timeline of short session ids, start times, status and observation counts, with key highlights and the decisions in each summary.
Needs:
agentmemory's memory server and MCP tools, plus its capture hooks recording your sessions: connecting the tools alone records no sessions.
Unlike recap:
That one takes a time window and groups sessions by date; this one lists the latest sessions.

Skill 5 of 8 in the agentmemory bundle, after forget and before recap.

TL;DR

Part of agentmemory, a memory server that records what coding agents do in each session as observations. session-history shows what happened in recent sessions on the current project. The agent asks the server for the project's sessions by its exact identifier, and for one agent's when you ask; when the identifier is unknown it pages through all sessions and matches their working directory to this project by whole directory, never substituting another project. It lists the most recent 20 in reverse chronological order with each one's short id, project, start time and status, the type and title of its key observations, their total, and, when a summary exists, its title and key decisions. A partial page is labelled as one. Only sessions the tool returned are shown: an empty history is reported as empty, not filled in from the conversation.

Summarizes the skill at f0f7378.

npx skills add https://github.com/rohitg00/agentmemory --skill session-history

skills.sh pageSource on GitHubAll skills from rohitg00/agentmemory

Total Downloads
14,400 on skills.sh, Nov 9, 2026
Repo stars
30,216 rohitg00/agentmemory
First seen
Apr 7, 2026 on skills.sh
Weekly Downloads
259
-35% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 21396
Sep 28374
Oct 5344
Oct 12315
Oct 19327
Oct 26318
Nov 2300
Nov 9259
Category
category:agentscategory:software-engineering

Build agents, orchestrate workers and give agents memory.

Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type
type:tool

Operates a CLI, API, app or bundled script to get something done.
Effect
effect:none

Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs
needs:mcp

Needs an MCP server connected.
Publisher
by:official

A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics
memory
Stack
stack:agentmemory

SKILL.md

From rohitg00/agentmemory at f0f7378. Checked daily, last changed Nov 6, 2026.

Frontmatter
name: session-history
description: 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.
user-invocable: true

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-IP

Why

Only show sessions and observations the tool returned. An empty history is a real answer, never a cue to invent past work.

Workflow

  1. 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.
  2. 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.
  3. For sessions with observations, show the key highlights (type plus title).
  4. Note the total observation count per session.
  5. 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.