By nicknisi
Recall, summarize, and analyze past AI coding sessions across multiple tools. Resume work by loading session context, generate daily standup and weekly summaries of coding activity, and view usage metrics like session counts, tool usage, and active hours.
Load a context primer for the current repo before starting work. Use when the user says "what was I doing here", "catch me up on this repo", "context primer", "what's the open thread", "where did I/we leave off" — and PROACTIVELY when a session opens on work that clearly continues something ("keep going on the refactor", "finish the migration") or when resuming a codebase after a break. Past sessions carry the open thread, prior decisions, and abandoned approaches that code and git history don't show.
Recall what was done on a specific project or topic from past AI coding sessions. Use when the user says "what did I do on [project]", "recall [topic]", "history of [project]", "when did I last work on [thing]" — but also when they reference prior work without asking for history explicitly: "didn't we already fix this", "what was that approach we tried", "why did we do it this way", "what happened to [file/feature]". Use PROACTIVELY before re-deriving a decision or re-solving a problem a past session likely settled — past conversations hold rationale and dead ends that never made it into git.
Show usage metrics and analytics for AI coding sessions. Use when the user asks "how much have I been coding", "session stats", "show me metrics", "tool usage", "which tool do I use most", "active hours", or wants analytics about their AI coding tool usage.
Generate a quick standup summary of yesterday and today's AI coding sessions. Use when the user says "standup", "what did I do yesterday", "daily summary", "what have I been working on", or needs a quick recap for a standup meeting.
Generate a comprehensive summary of AI coding sessions from the past week. Use when the user says "weekly summary", "what did I do this week", "summarize my week", "weekly recap", "week in review", or asks for a summary of recent work across projects.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Search and memory across your AI coding sessions.
One index over Claude Code, Codex, Pi, and OpenCode — fuzzy-find and resume past sessions from the CLI, give agents recall over prior work via MCP, and see where your tokens go.
Every AI coding session leaves a transcript behind. Claude Code buries them in ~/.claude/projects/, Codex and Pi have their own layouts, OpenCode keeps everything in a SQLite database — and everything in them (what you tried, what you decided, what broke) is effectively write-only.
sessions builds a full-text search index over all of it and makes that history useful in three ways:
brew install nicknisi/formulae/sessions
Or, equivalently:
brew tap nicknisi/formulae
brew install sessions
git clone https://github.com/nicknisi/sessions && cd sessions
bun install && bun run build
The compiled binary is at dist/sessions. Requires Bun when building from source. The Homebrew install is a standalone binary — no runtime needed.
brew install fzf.After installing, run:
sessions setup
This automatically:
~/.local/share/sessions/plugin/❯ sessions setup
sessions setup
✓ Plugin installed to ~/.local/share/sessions/plugin/
✓ MCP server added to Claude Code
✓ Plugin registered with Claude Code
✓ MCP server added to Cursor
✓ Plugin registered with Cursor
Skills available:
/context Context primer for the current repo
/weekly-summary Summarize your past week's AI sessions
/standup Yesterday + today activity for standups
/recall What did I do on a specific project?
/session-metrics Usage dashboard with tool breakdown
Run `sessions setup` again after upgrading to update skills.
After upgrading sessions (e.g., brew upgrade sessions), run sessions setup again to update the skills to the latest version.
To remove everything: sessions uninstall
sessions # Browse all sessions with fzf
sessions <query> # Full-text search across session content
sessions --here # Scope to current git repo only
sessions --tool claude # Filter to Claude Code sessions only
sessions --errored # Only sessions that hit an error
sessions --file src/auth.ts # Only sessions that touched this file
sessions context # Print a context primer for the current repo
sessions digest <session> # Print one session's arc as compact markdown
sessions report # Usage report (HTML dashboard, opens in browser)
npx claudepluginhub nicknisi/sessions --plugin sessionsEssential agents, commands, and tools for enhanced Claude Code workflows - git commits, code simplification, brainstorming, security audits, thermo-nuclear code-quality review, PR creation, and codebase sweep.
Agent dashboard TUI — tracks AI agent state via hooks for the fleet CLI
Transform brain dumps into implementation specs through an evidence-gated interview stress-tested by adversarial plan critics. Interactive HTML contract for planning decisions, Markdown specs for execution. One door in: the interview routes to full artifact review or an express finish on an isolation branch; /ideation:autopilot runs all phases on a deterministic workflow engine with overlap-serialized parallel waves; completed watched runs capture learnings inline that future interviews read and apply visibly.
Persistent local memory for Claude Code. Every tool call, every file edit, every thinking block from every session — stored verbatim on your machine. Semantic recall in ~126ms with zero API calls.
Agentic memory — search and summarize coding-agent sessions, plans, and memory across projects
Meta-Cognition tool for Claude Code with 22 MCP tools for session history analysis, error tracking, quality scanning, work patterns, timelines, and bug detection. Focused, fast, and data-driven.
Use ctx to search local coding-agent history and retrieve cited session context before working.
Search across Claude Code and OpenClaw session history. Find past conversations, decisions, and code snippets instantly.
qrec session recall engine