All projects

PROJECT 03 / Developer Analytics & Project Memory

TraceLens

Offline Codex analytics with traceable usage, validation evidence, and project memory for the next session.

TraceLens analyses Codex session logs and keeps reviewed project memory in CHATGPT.md; Wakeline analyses Claude Code usage, costs, and coding friction.

WHEN

2026

CONTRIBUTION

Design & development

TECHNOLOGIES
PythonSQLiteHTMLJavaScriptCodex
LOCAL ANALYTICS & MEMORY03
SELECTED CODEX SESSION LOGSEvidence into context
Python · local SQLite metadataSession evidence → offline dashboard
Reviewed context → CHATGPT.md
UsageValidationReworkMemory

Conceptual local evidence workflow

THE PROJECT AT A GLANCE

Understand the work. Carry the context forward.

Explicitly selected Codex logs become local metadata, an interactive offline dashboard, and optional reviewed project memory.

Usage views
3
Loop finding types
5
Automated tests
344

01 / OBJECTIVE

What the project set out to do

Make Codex work easier to inspect across sessions: explore usage and repeated work, distinguish conversation completion from validation evidence, and retain useful project context locally.

02 / MY CONTRIBUTION

My part in the work

I developed TraceLens as a Python analytics engine with a self-contained HTML dashboard and portable Codex plugin. It normalizes selected session logs into SQLite metadata, generates evidence-backed reports, and optionally maintains per-project CHATGPT.md memory files.

The engineering focus is evidence and continuity: link findings to recorded events, preserve reviewed context through refreshes, and report the limits of observed results and estimated measurements.

03 / TECHNICAL APPROACH

How it came together

01

Normalize explicitly selected session logs

Read bounded Codex JSONL records, normalize supported events, deduplicate observations, and update existing session snapshots in a local SQLite store. Transcript commands are analyzed as data rather than executed.

02

Make usage and working patterns explorable

Embed data and assets in one offline HTML dashboard with project search, model and date filters, token charts, tables, heatmaps, and session timelines. Provide keyboard-focus and tap readouts alongside chart views.

03

Keep outcomes tied to captured evidence

Track chat and validation states separately, with supported tool results, check attempts, file references, commit evidence, and parsing warnings. Rework and loop findings link back to their supporting records.

04

Carry reviewed project context forward

Generate stable per-project memory files with recorded activity and optional reviewed goals, decisions, completed work, and next steps. Preserve personal notes outside managed blocks and retain reviewed context on activity-only refreshes.

04 / OUTCOMES

What the work produced

  • Built a local workflow from selected Codex transcripts to SQLite metadata and interactive reports.
  • Connected usage, validation, and repeated-work findings to supporting session evidence.
  • Added project browsing and reviewed memory that can be refreshed without replacing personal notes.

Costs and active time are estimates. Loop and rework findings flag patterns to review; they do not prove wasted effort or correct code, and missing logs can leave gaps. Reports stay local. The Codex plugin still needs a complete check inside the app.

UP NEXT / PROJECT 04

Wakeline

View case study

Want to talk about this project?

Get in touch