Agents Recap — AI skill for Claude Code
Local, offline recap and RAG memory of your AI coding sessions.
How to install Agents Recap
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open emihiggins/agents-recap and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Agents Recap does
Local, offline recap and RAG memory of your AI coding sessions. Reads Claude Code, Cursor and VS Code Copilot Chat session state read-only, tells you where you left off, and lets you ask about it later.
Alternatives in AI
- Academic Humanizer — Strip AI-writing tells from papers and grant proposals (NSF/NIH), while keeping scholarly voice and tying clai 1.1k ★
- Late CLI — High-performance AI agent for long-horizon tasks and local models 442 ★
- Cross Agent Session Resumer — Resume AI coding sessions across providers: converts Codex, Claude, Gemini, and other session formats through 71 ★
README
agent-recap
You had six AI sessions going. Which one still has work in it?
`agent-recap` reads the session state your AI tools already keep on disk, works out where each project actually stands, and writes one HTML page telling you where you left off. It also remembers that context so you can ask about it later.
Everything runs locally against [Ollama](https://ollama.com). No API keys, no network calls, nothing leaves the machine.
agent-recap # build the recap and open it
agent-recap ask "what was I doing with the rates API?"
agent-recap status # what's running right now
agent-recap schedule --at 08:30 # have it ready before you sit down

*Sample data. Regenerate with `python scripts/sample_recap.py`.*
It leads with what's actually blocking you:
Waiting on you
storefront-web — permission prompt, waiting 48m
An agent stalled on a permission prompt for the last three quarters of an hour is the single most useful thing this can tell you, so it gets a banner.
What it reads
| Source | Where | What it gets |
|---|---|---|
| Claude Code | ~/.claude |
Live session status, titles, last messages, plan documents and their remaining steps |
| Cursor | Cursor's global state.vscdb |
Composer/agent sessions, titles, agent todo lists, context usage |
| VS Code Copilot Chat | VS Code workspaceStorage |
Chat sessions (both the legacy and journal formats), Copilot todo lists |
| git | each project directory | Branch, uncommitted files, unpushed commits |
All of it is opened **read-only**. Cursor and VS Code are usually running while this executes, so connections are opened with `mode=ro` and the test suite asserts that writes and DDL are rejected. `agent-recap` never modifies another tool's data.
Getting started
**Requirements**
- macOS. All the
Related Skills
Pbi Resume
Restore session context and continue from where you left off. Reads .pbi/context.md to reconstruct model state
Project Recap
Generate a visual HTML project recap — rebuild mental model of a project's current state, recent decisions, an
Session Handoff Skill
Seamless AI session handoff: preserve context across conversations so agents pick up where they left off — zer
AI Quota Meter
Claude Code knows how much quota you have left on nearly every turn, and only shows you if you ask. This puts
Foundling
An AI that wakes every day with no memory, reads what its past selves left behind, adds one small mark, and fo
Gentle Agent State
See which AI coding agent needs you — right in your tmux tab bar. A colored dot per window (working/blocked/id
Related Agents
10x Tool Calls
Cursor and Windsurf meter usage by requests and tool calls rather than tokens, which means a finished or stall
Demo Planner
Plans a realistic VS Code demo scene based on tip card content. Reads tip text, understands the concept, and g
Brainstem Copilot.Agent
One native Copilot chat with both Brainstem and Brain Surgeon. Address either by name to use capabilities or t