Workflow Recorder
Sign in →
🔥 Beta · open to the first 50 builders

Log your builds.

A Strava-style profile for your Claude Code sessions. Every session auto-captures — duration, tokens, tool counts, commits — and turns into a shareable card. Nothing about your prompts or code ever leaves your machine.

$ npx @workflowrecorder/buildlog init
30 seconds · Sign in with GitHub · Works with Claude Code CLI on macOS, Linux, Windows
What a shared session looks like
@maya · app.workflowrecorder.com/s/a4b91● public

9h 51m · 852 tools · 22 commits

Apr 14 · Opus 4.7
9h 51m
active
852
tools
22
commits
556.1M
tokens
$1229.87
spend
“9h 51m in workflow-recorder-web. Heavy on Bash + Read. Shipped 22 commits.”
Bash × 403Read × 92TaskUpdate × 86Edit × 83Write × 47
How it works
1
Install once
npx @workflowrecorder/buildlog init signs you in with GitHub, appends a Stop hook to ~/.claude/settings.json, and optionally imports your last 7 days of sessions.
2
Keep coding
Every time Claude Code finishes responding, the hook fires — silently parses the session's metadata, computes stats, uploads. No prompts, no dialogs, no "save?" interruptions. You don't know it happened.
3
Share when you want
Sessions are private by default. Visit your profile, tap "Make public" on the ones you want to share, copy the URL, drop it in Discord / Twitter / wherever. Lurkers see the card without signing in.
What we see · what we never see
We capture
  • Session duration (active, excluding idle gaps > 30 min)
  • Tool counts: { Read: 12, Bash: 8, Edit: 5 }
  • Token counts per session (input / output / cache)
  • Number of files touched, number of commits made
  • Model used (Opus / Sonnet / Haiku)
  • Project name hash (display name stays local to you)
We never capture
  • Your prompts or Claude's responses
  • File contents or diffs
  • File paths
  • Bash command outputs
  • Tool call arguments
  • Screenshots or any visual data
Ready? Run npx @workflowrecorder/buildlog init or sign in to see your profile →