whatisgithub

What is tracebench?

skandesh/tracebench — explained in plain English

Analysis updated 2026-05-18

1TypeScriptAudience · developerComplexity · 2/5LicenseSetup · easy

In one sentence

A local viewer that collects session logs from AI coding tools like Claude Code, Codex, and Cursor into one shared timeline and cost dashboard.

Mindmap

mindmap
  root((tracebench))
    What it does
      Reads agent logs
      Shared timeline view
      Local only viewer
    Tech stack
      TypeScript Fastify
      SQLite storage
      React Vite UI
    Supported tools
      Claude Code
      Codex
      Cursor
    Use cases
      Compare sessions
      Track token cost
      Debug agent actions

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

View and compare session logs from Claude Code, Codex, and Cursor in one local dashboard.

USE CASE 2

Estimate token costs across multiple AI coding assistants from a single tool.

USE CASE 3

Debug what an AI coding agent did during a session by browsing its timeline of actions.

USE CASE 4

Write a new adapter to add log support for another AI coding tool.

What is it built with?

TypeScriptNode.jsFastifySQLiteReact

How does it compare?

skandesh/tracebench0xkinno/neuralvault0xmayurrr/ai-contractauditor
Stars111
LanguageTypeScriptTypeScriptTypeScript
Setup difficultyeasyhardeasy
Complexity2/54/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

So what is it?

Tracebench is a local tool that lets you browse and review the session logs produced by AI coding assistants. If you have used Claude Code, Codex, or Cursor on your computer, each of those tools quietly writes a log of everything it did during a session: which files it read, what commands it ran, how many tokens it consumed. Tracebench picks up those logs and shows them in a single web-based viewer that runs entirely on your own machine, with no data sent anywhere. You start it with one command, npx tracebench, and it opens a browser tab at a local address. On first launch it scans the standard locations where Claude Code, Codex, and Cursor store their logs, loads everything into a small local database, and presents a three-pane interface. You can see a timeline of every action the agent took, browse sessions across different tools side by side, and review cost estimates based on token counts. The project is built around the idea that most people use more than one AI coding tool, yet existing log viewers are each tied to a single tool. Tracebench introduces a common format that all supported agents convert into, so the same timeline view works regardless of which assistant produced the session. Adding support for a new tool means writing one adapter module that converts its log format into that shared format. Under the hood the server is a lightweight Node.js process using Fastify, storing indexed sessions in SQLite. The front end is built with Vite and React. The codebase is split into six packages: a core library with the shared schema and pricing calculations, one adapter per supported agent, the server, and the UI. The project is at an early version and marks certain adapters as planned rather than available. The roadmap includes context window analysis, cost dashboards, and a plugin system for community-built adapters. The source is released under the Apache 2.0 license.

Copy-paste prompts

Prompt 1
Help me run npx tracebench and view my Claude Code session logs locally.
Prompt 2
Explain how Tracebench's shared log format works across different AI coding tools.
Prompt 3
Show me how to write a new adapter module for a coding tool not yet supported.
Prompt 4
Walk me through the six packages in this codebase and what each one does.

Frequently asked questions

What is tracebench?

A local viewer that collects session logs from AI coding tools like Claude Code, Codex, and Cursor into one shared timeline and cost dashboard.

What language is tracebench written in?

Mainly TypeScript. The stack also includes TypeScript, Node.js, Fastify.

What license does tracebench use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is tracebench to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is tracebench for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.