what the claude

~/.claude/projects $ what-the-claude

What the did I do today?

You ran a dozen agents this week and lost the thread of all of them. Claude Code wrote down every session as it happened. what the claude reads those logs out of ~/.claude/projects and draws your week back: which project, which hour, how many tokens.

Launch what the claude View on GitHub

Nothing to install, no sign-up. It opens your folder in this tab.

the week below 216h active 6 projects 87% cache

what the claude · week of Jun 01–07
A weekly calendar in what the claude. Monday through Sunday columns are filled with colored blocks for each project, stacked by the hour, with a per-day totals breakdown along the bottom.
// HOW IT WORKS

It runs on the logs Claude Code already keeps.

  1. ~/.claude/projects

    Claude Code already writes a transcript for every session in here. That pile of .jsonl is the whole input.

  2. read in the tab

    Grant the folder once and it parses every transcript locally, in your browser. No server stands behind it, nothing uploads, no API key.

  3. your week, drawn

    Sessions cluster into work blocks by project, carrying their tokens and models, and the calendar keeps filling in as you work.

// WHAT YOU SEE

Every session, as the block of work it actually was.

Real work blocks, not message pings

Scattered sessions cluster into the stretches you actually worked, from the first prompt to the last reply. A block is a real sitting, not one mark per message.

Open any block

The full event timeline, the git branch you were on, idle gaps, and a per-session token sparkline. The whole sitting, not a summary.

/b/… · session detail
A what-the-claude session detail card titled 'what the claude': the date, duration and message count, a token mix bar, a 95% cache-hit pie, and a five-cell grid of total, input, cache write, cache read and output tokens with the model tag claude-sonnet-4-6.
every token: input, cache read/write, output, per block
cache-hit rate and the model that ran
// GROUPING

Five folders, one project.

Every session happens in a folder. By default each folder is its own row, so one project spread across api, web and infra lands as three separate lines with the hours split between them. A project is just a label on one or more folders: they share a colour, and their time adds up.

before · raw folders
~/dev/acme/api1h
~/dev/acme/web2h
~/dev/acme/infra20m
after · one project
acme3h 20m
api, web and infra: summed up, one colour.

On first run it guesses sensible projects for you. Rename, merge or recolour anything by right-clicking it on the calendar, and nothing is permanent.

[ PRIVACY ]

Your transcripts never leave your machine.

what the claude is one static HTML file. It reads your logs with the browser's File System Access API and renders them in the tab. There is no server to upload to, no account to create, and nothing is sent anywhere. Read the source and check.

Live folder access needs a Chromium browser (Chrome, Edge, Arc). Firefox and Safari can't open a live folder yet, so they read a one-shot snapshot you re-pick to refresh.