● live · cookd.lol

Cookd

The anti-social network for people who use Claude too much.

Reads your Claude Code usage on your own machine and turns it into a nightly paper: tokens, sessions, streaks and the habits behind them.

cookd.vol. 001 · the daily paper of people who ran out of prompts · sample
100% WINDOW USAGE, AGAIN

Sources close to the user confirm “one more fix” was said at 01:40, 02:15 and 03:02.

The editor notes the subagents worked harder than their manager. Again.

/how-it-works

How Cookd works

  1. 01Your machineClaude Code already keeps logs of your sessions, locally.
  2. 02CountCookd de-duplicates them properly, keeps subagents apart and labels every estimate.
  3. 03WhitelistOnly counts get through. Prompts, responses, code and file names are never read.
  4. 04The editorAn AI editor writes tonight’s edition from the numbers, with no mercy.
  5. 05The paperYour nightly paper: in full colour, with a barcode.
/under-the-hood

Under the hood

in
Claude Code session logs, on your machine
Your prompt history (counts only)
The local analyser
De-duplicationeach message counted once, at its final size
Whitelistcounts in, content never
Estimates, labelledno real dollars exist in the logs, so none are claimed
AI editorwrites the edition from the numbers alone
out
Your nightly paper
how it uses AI
  • Usage analytics over local Claude Code logs, de-duplicated and counted carefully, with every estimate labelled as one.
  • An AI editor that writes each edition from the numbers.
  • Strict whitelisting: Cookd counts your activity but never reads prompts, responses, code or file names.
for

Developers who live in Claude Code and want an honest, funny look at how they use it.

the line it holds

Count everything, read nothing: no prompt, response or file content ever leaves the whitelist.

/why-its-hard-to-copy
Careful countingMost usage tools double-count. Cookd’s numbers are measured against real logs, and estimates say they are estimates.
Private by constructionA whitelist, not a filter: content can’t leak because it is never read.
A tone people shareBeing roasted by your own paper is the kind of thing people post.
/also from codeclowns