CodeSeshv1.4.1
Local / Zero config / 19 agents

Search and replay
your AI coding history.

Search and replay local history from Claude Code, Codex, Cursor, and 16 other agents. Browse messages, tool calls, and file changes by project.

Session content and indexes stay local. No account, cloud sync, or session telemetry.

Reads sessions from

01Tour

The whole story.
In one place.

Explore a working sample. Change the date range, open a project, or step through a conversation.

Sample data
Overview10-09 → 10-15
Range
Last 7 days
2026-10-09 – 2026-10-15 · 3 agents · 6 projects · vs previous 7 days
Tokens▲ 12%
412.6M
58.9M/day · 97% cache hits
API valueEst.▲ 8%
$286.40
$40.91/day
Sessions▼ 6%
64
4,812 messages · 75.2/session
Token mix412.6M
Input3.1M0.8%
Output1.9M0.5%
Cache write5.2M1.3%
Cache read402.4M97.5%
Daily tokensInputOutputCache writeCache readAPI value
38M
52M
61M
95M
74M
48M
44M
10-0910-1010-1110-1210-1310-1410-15

02Capabilities

Discover, organize, recover, replay.
History becomes useful after all four.

CodeSesh follows the real loop of AI-assisted engineering work.

01

Discover

Bring local sessions from different agents into one index.

  • Zero configuration

    Run one command and scan supported agent sessions on your filesystem.

  • Unified timeline

    Browse histories from 19 AI coding agents in one interface.

  • Live refresh

    Add local session changes to the index without restarting the UI.

02

Organize

Put sessions back into project, task, and engineering context.

  • Project and session tree

    Group by repository and keep subagent sessions under their parent.

  • Smart tags

    Label fixes, refactors, features, tests, docs, planning, and more.

  • Session aliases

    Give key sessions memorable names that persist in search and bookmarks.

03

Recover

Bring old decisions, paths, and context back into the current task.

  • Structured global search

    Search titles, messages, tool output, and paths, then filter the results.

  • File activity index

    Start with a file and find sessions that read or changed it.

  • Keyboard navigation

    Switch views, focus search, and move through groups from the keyboard.

04

Replay

Reconstruct the full path from problem to result.

  • Full conversation replay

    Keep messages, tool calls, and reasoning steps in sequence.

  • Cost and token visibility

    Compare tokens, cache hits, recorded cost, and model estimates.

  • Local SQLite index

    Use one local database for fast restore, search, and schema migrations.

03Data boundary

Your history.
On your machine.

Your sessions and search index stay on your computer by default. No account. No session telemetry. Free and open source.

Read about your data
Your machine
  1. Agent logs
    ~/.claude · ~/.codex · …
  2. CodeSesh scan
    Rust · incremental
  3. SQLite index
    messages · FTS · cost
  4. Web UI
    localhost:4521
Cloud upload
never in standalone mode

Optional Workers send sessions to a Hub you host yourself. Attachments and source files are never transferred.

04Multi-machine

Many machines.
One history.

Run a Hub where you browse, and pair a Worker on each computer you code on. Workers collect locally and upload to your self-hosted Hub. The Hub handles search, cost estimates, and the Web UI.

  1. 01

    Pair once

    A one-time token, valid for 10 minutes, becomes a revocable per-node credential. The Hub stores only its digest.

  2. 02

    Keeps working offline

    When the Hub is unreachable, Workers keep collecting, queue uploads on disk, and catch up after reconnecting.

  3. 03

    See every source

    The source-node panel shows collection progress and errors, starts rescans, and replaces Workers. Background services run on macOS, Linux, and Windows.

Collect history from multiple computers

05Agents

Different agents.
Same workspace.

19supported agents

Each agent connects through a core adapter and contributes to one index of sessions, projects, search, and file activity.

  • Claude Code
  • Qoder
  • Qoder CN
  • Cursor
  • Droid
  • Kimi-Cli
  • Kimi-Code
  • Codex
  • Grok
  • Pi
  • oh-my-pi
  • OpenCode
  • ZCode
  • MiniMax Code
  • DSH
  • DeepChat
  • Cherry Studio
  • Antigravity CLIPartial
  • Gemini CLI

Support levels reflect what each adapter actually parses from sessions, usage, and tool calls.

06Updates & guides

Follow the product,
not the commit log.

See the improvements that change how CodeSesh feels to use, plus the principles guiding what we build next.

Latest updatev1.4.1

Faster Chinese search and less work while idle

CodeSesh 1.4.1 makes Chinese session search faster on large local AI coding histories, reduces background scanning and retained memory, and keeps live updates from piling up during slow requests.

  • Find Chinese history with fewer reads
  • Do less work in the background
  • Retain less data after activity stops
  • Keep DeepChat references in replay
Read the product changelog

07FAQ

Frequently asked questions

Answers about CodeSesh, installation, data boundaries, and large histories.

What is CodeSesh?

CodeSesh is a local developer tool for discovering, aggregating, searching, and replaying AI coding session history. It turns local records from Claude Code, Qoder, Qoder CN, Cursor, Droid, Kimi-Cli, Kimi-Code, Codex, Grok, Pi, oh-my-pi, OpenCode, ZCode, MiniMax Code, DSH, DeepChat, Cherry Studio, Antigravity CLI, and Gemini CLI into a project-aware engineering memory layer.

Does CodeSesh upload local AI session data?

In default standalone mode, session data stays on your computer in a local SQLite index. Optional Workers send session content and metadata, including paths, usage, and costs, to your configured self-hosted Hub. Attachments and source files are not transferred. No account is required, and no session telemetry is collected.

How do I install and start CodeSesh?

Run npx codesesh in a terminal. CodeSesh scans supported local AI coding sessions and opens its Web UI at http://localhost:4521. If the default port is busy, it tries the next available port. The npm launcher requires Node.js 22 or later. The standalone native executable does not require Node.

Session history guide

Why is a session missing?

CodeSesh opens with sessions active in the last 7 days and keeps scanning older history in the background. Switch the time range in the UI to 30 days, 90 days, All, or a custom range to see older sessions. Until the first scan finishes, older records may be incomplete. If a session is still missing, check the agent filter, source files, and custom data directories. CodeSesh cannot recover deleted source records.

Troubleshoot missing sessions

How does CodeSesh stay responsive with a large history?

The first scan persists backfill progress and can resume after interruption. Later starts restore from the local SQLite cache, while file watchers incrementally update changed sessions. Long conversation timelines use viewport virtualization instead of rendering every message at once.

08Install

Keep the context.
Start here.

One command opens your local coding history. Choose the installation method that works for you. Open source, free, and your session data stays local.

Installation method

npx codesesh@latest

macOS / Linux / Windows · Node.js 22+
Update: npx codesesh@latest