# Session History

Show what happened in recent past sessions on this project as a clean timeline.

- Repository: https://github.com/rohitg00/agentmemory (30072 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rohitg00/agentmemory --skill session-history -g -a claude-code -y`
Codex: `npx skills add rohitg00/agentmemory --skill session-history -g -a codex -y`
Cursor: `npx skills add rohitg00/agentmemory --skill session-history -g -a cursor -y`
Gemini CLI: `npx skills add rohitg00/agentmemory --skill session-history -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add rohitg00/agentmemory`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

The user wants an overview of recent sessions on this project.

## Quick start

```json
memory_sessions { "project": "<current-project-id>", "limit": 20 }
```

Expected output:

```text
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.

The rest: https://github.com/rohitg00/agentmemory/blob/HEAD/plugin/skills/session-history/SKILL.md