Launched this week
Chit reads the Claude Code transcripts already on your disk and prints the day back as a receipt, grouped by project and ready to paste into a standup. A 777 KB Mac app. No Hammerspoon, no Python, no account, and no network code in the binary at all.
Notchling
Couch
@ravindra_sisodia1 This looks real cool. how big is the file it make for the day?
Notchling
@matthew_gladyshev You've got it — no model call anywhere, and no network code in the binary at all. Claude Code writes its own aiTitle for most sessions into the transcript JSONL, and Chit just reads it.
When a session has no title, Chit falls back through what it actually did: the description Claude Code writes for each Bash call, then files changed, then files read. It never uses your prompts for display.
If you're building on the same data: it's line-delimited JSON, and aiTitle, the Bash description and the file paths in Edit/Write inputs carry most of the signal. Do a plain substring search on each line before you JSON-decode it — that's most of why Chit gets through a few GB of transcripts in well under a second.
Bababot
The CLI option makes this more interesting to me. Being able to pipe the output into another workflow means i wouldnt have to change how i already handle timesheets.
Notchling
@adams_parker That's exactly why the CLI exists — a few people emailed after my last launches asking to pipe it into their timesheets. It's plain text to stdout:
chit --today
chit --today --markdown
Past days and ranges work the same way (chit --date=2026-09-25, chit --from=… --to=…) — those are part of Pro. Use the = form for dates; the installer puts chit on your PATH, so it works straight away.
Any chance this can run on codex too?
Notchling
@alexcheeseman1 Not today — Chit reads Claude Code's transcript format specifically. Codex keeps its own session logs in a different shape, so it would be a second reader rather than a setting. The engine is basically a fast parser, so it's very doable. Would you use it alongside Claude Code, or instead of it?
is it only for Mac? or Windows too?
Notchling
@luca_ardito Mac only for now (macOS 13+, Apple Silicon and Intel). No Windows version planned right now — Chit reads Claude Code's local transcript format directly, so a Windows port isn't a huge lift if there's demand, just haven't built it.
Can it be used to track time and bill projects — e.g. export the day as a timesheet? Is there a machine-readable export (CSV/JSON)?
Notchling
@tomasz_stryczynski Honest answer: not for billing hours, and I'd rather say that than have you find out on an invoice. Chit records what you did and when each piece started, but it isn't a time tracker — how long a session was open isn't billable time, and I don't want it pretending otherwise.
There's no CSV or JSON yet either. Output today is plain text or Markdown, from Copy all or the CLI (chit --today, --markdown). A JSON flag on the CLI is the obvious next thing. If you tell me which fields you'd bill from — project, description, start time, something else — that's what I'll build it around.
This is just great. I’m way out of my league here….learning to code in Python, learning terminal, all the things….and most of it is done with the help of Claude Code at the command line or through VS code….i work though the day (roofing contractor) put the kids to bed and get to work on whatever the current assignment is in CS50P (free Harvard Python). Working 10-2am, falling asleep and it’s all gone the next morning😂. Really excited to see if this prompts recall….thank you for the cool product and I love your branding!
Notchling
@rewoodworks This genuinely made my day, thank you. Good luck with CS50P — the fact you're shipping real code at 1am after roofing all day is the whole reason I wanted a receipt that remembers for you.