Sessiongrep — Development skill for Claude Code
Local-first memory layer for CLI agents.
How to install Sessiongrep
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open braincompany/sessiongrep and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Sessiongrep does
Local-first memory layer for CLI agents. Indexes Claude Code, Codex CLI, Cursor, Antigravity, and Pi sessions into SQLite + FTS5, searchable from a CLI, TUI, or MCP server.
Alternatives in Development
- Projectmem — Open-source coding agent memory 766 ★
- Coding Agent Session Search — Unified TUI and CLI to index and search your local coding agent session history across 11+ providers (Codex, C 708 ★
- Scope Recall Hermes — Local long-term memory for Hermes, Codex, Claude Code, WorkBuddy and dsh agents: one SQLite store, source-back 438 ★
README
sessiongrep
[](https://github.com/braincompany/sessiongrep/actions/workflows/ci.yml) [](LICENSE)
**You solved that bug last week. Your next agent session has no idea.**
A local-first memory layer for CLI agents. `sessiongrep` indexes your Claude Code, Codex CLI, Cursor, Antigravity, and Pi session histories into a single SQLite + FTS5 database, then gives you one CLI/TUI to find old work by topic, repo, provider, or recency. It also ships an MCP server so your agent can search its own history.
The real payoff is portable context: your session history isn't trapped in one tool. Work you started in Claude Code can continue in Codex, and an agent can recover — and even critique — its own prior reasoning across every tool you use.

Read the announcement: [Sessiongrep: a local-first memory layer for CLI agents](https://brain.co/blog/sessiongrep-a-local-first-memory-layer-for-cli-agents).
Why
Session transcripts already live on your machine — scattered across `~/.claude/projects`, `~/.codex/sessions`, `~/.cursor/projects` as noisy JSONL with opaque filenames. The information is not missing, it's stranded. Humans don't want to read it; agents don't know how to retrieve it. Grep over JSONL drowns in tool payloads. Shell history captures commands but not reasoning. Cloud-synced or vector-backed alternatives bring secrets and URLs into systems that aren't yours.
`sessiongrep` keeps recall local. One static binary, one SQLite file, no daemon, no server. The index is a disposable cache — delete it and rebuild it whenever you want.
How it works
Provider adapters normalize Claude, Codex, Cursor, Antigra
Related Skills
Flightlog
Total recall for Claude Code. MCP server that indexes conversation history into SQLite — search past sessions,
MCP Memory
🧠 Memoria local para agentes IA vía MCP. Drop-in para Claude Code, OpenCode, Cursor, Continue. Python + FastM
Codex Toolbox
Build one useful MCP server while learning how Codex tools, skills, hooks, subagents and permissions fit toget
Recallnest
One memory, every terminal. Shared memory layer for any MCP client — Claude Code, Codex, Kimi, Antigravity (ag
Kaectx
Local searchable store of your coding-agent sessions (Claude Code, Codex), served to any agent over MCP. Singl
Netvein
Local-first Chrome CDP reverse engineering & wire-level traffic MCP server, for Claude Code, Cursor, Codex, Op
Related Agents
Ade
Agent sessions routinely outlast the machine that started them, and checking a Claude Code or Codex run from a
Stripe Specialist
Stripe payments + billing — the money layer: the server Stripe client, product/price catalog, Checkout Session
Debug Memory Agent
Records resolved bug root causes, anti-patterns, and process lessons into MEMORY.md in a structured, searchabl