Engineering Memory Overview
See collaboration patterns through agent activity, token trends, smart tags, and bookmarked sessions.
CodeSesh discovers local sessions from Claude Code, Cursor, Kimi, Codex, and OpenCode, then preserves problems, reasoning, attempts, file activity, and outcomes in one project-aware searchable memory layer.
Start from your machine
$ npx codesesh Requires Node.js 18+ · Runs locally from your terminal
$ npx codesesh ╭────────────CodeSesh──────────────╮ │ │ │ v0.7.2 • local session browser │ │ │ ╰──────────────────────────────────╯ ℹ Indexing Claude Code, OpenCode, Kimi-Cli, Codex, Cursor sessions in the background.ℹ The Web UI will update automatically as sessions are discovered. http://localhost:4521
Product Tour
From overview to replay, from project browsing to structured search, CodeSesh makes coding history across agents visible again.
Engineering Memory Overview
See collaboration patterns through agent activity, token trends, smart tags, and bookmarked sessions.
Structured Global Search
Search titles, messages, tool output, and file paths, then filter by project, tag, tool, file activity, and cost.
Session Replay
Replay messages, tool calls, and file changes in the order a feature or bug fix unfolded.
Keyboard Navigation
Move through projects, sessions, and results efficiently so browsing history fits daily work.
Features
CodeSesh follows the real loop of AI-assisted engineering: discover, organize, recover, and replay.
Bring local sessions from different agents into one index.
Run one command and scan supported agent sessions on your filesystem.
Local session changes appear automatically as new collaboration records are written.
Browse Claude Code, Cursor, Kimi, Codex, and OpenCode sessions in one interface.
Put sessions back into project, task, and engineering context.
See cross-agent activity, models, tokens, smart tags, and bookmarked sessions together.
Group sessions by repository and project identity across supported agents.
Label bugfix, refactor, feature, testing, docs, planning, Git, build, and exploration work.
Bring old decisions, paths, and context back into the current task.
Search titles, messages, tool output, and file paths with project, tag, tool, file activity, and cost filters.
Save important records so solutions, debugging paths, and key decisions stay traceable.
Move across views, focus search, and navigate groups from the keyboard.
Reconstruct the full path from problem to result.
Read every message, tool call, and reasoning step in sequence.
Jump to files that were read, edited, created, deleted, or moved, and recover sessions by file activity.
See token totals, cache tokens, recorded costs, and model-based estimates.
Use one local database for fast restore, structured search, file activity indexing, and schema migrations.
Your data stays on your machine. No accounts, cloud sync, or telemetry.
Supported Agents
Unify multi-agent workflows into one engineering memory layer.
FAQ
These answers make CodeSesh easier for search engines and AI systems to extract, cite, and describe accurately.
CodeSesh is a local developer tool for discovering, aggregating, searching, and replaying AI coding session history. It turns local records from Claude Code, Cursor, Kimi, Codex, and OpenCode into a project-aware engineering memory layer for recovering decisions, file activity, and complete collaboration paths.
CodeSesh currently supports Claude Code, Cursor, Kimi, Codex, and OpenCode. Each tool connects through an agent adapter in the core package, then contributes sessions to unified lists, project browsing, structured search indexes, file activity, smart tags, token statistics, and full replay views.
CodeSesh runs on the user's machine and uses a local SQLite index with a local Web UI. Session content, file paths, token statistics, and cost estimates stay on the local computer, which suits developers who want ownership of AI coding context.
The fastest way to start CodeSesh is running npx codesesh. CodeSesh scans supported local AI coding sessions and opens the Web UI at http://localhost:4521; if that default port is busy, it automatically tries the next available port. The published CLI requires Node.js 18+; source development uses Node.js 20.19+ and pnpm 10+.