Vibe coding
with a paper trail
You talk to Claude. Code appears. But who tracks that work? Scribe captures every vibe coding session — the conversation, the commits, the files — and turns it into a billable timeline.
Vibe coding changes how work looks
Traditional time trackers weren't built for AI pair programming. Scribe is.
Legacy time trackers
- ✕Track keystrokes and mouse clicks
- ✕Penalize fast AI-assisted output
- ✕Can't see AI conversation context
- ✕Manual categorization for every task
- ✕Vibe coding sessions look like idle time
Scribe for vibe coding
- Tracks AI conversations as first-class work
- Values output over activity metrics
- Links conversations to resulting commits
- Automatic project detection from paths
- AI sessions show as productive work time
Every vibe coding session, captured
Scribe sees the full picture: what you asked, what changed, and when it happened.
Conversations
Claude Code session logs parsed with timestamps. Each conversation is a work event linked to the project directory where it happened.
Commits
Git history from every repo you work in. AI-generated commits and manual ones alike, all with diffs and complexity scores for time estimation.
File Changes
Filesystem modification timestamps that fill in gaps between conversations and commits. Config files, assets, docs — it all counts.
Built for the vibe coding era
Most time trackers measure how busy you look. Scribe measures what you actually built. In the vibe coding era, a 20-minute AI conversation can produce more than a full day of manual coding. Scribe captures that reality.
- AI conversations are billable work events
- Complexity-based time estimation, not keystroke counting
- Local-first — your code and conversations stay private
- Desktop app runs silently in your system tray
Native parsing
100% local
No timers needed
macOS native
Vibe coding FAQ
What is vibe coding?
Vibe coding is writing software by conversing with AI instead of typing code directly. You describe what you want in natural language, the AI generates the code, and you iterate until it's right. It's the day-to-day practice of vibe engineering — using tools like Claude Code, Cursor, or Copilot as your primary coding interface.
How does Scribe track vibe coding sessions?
Scribe reads Claude Code conversation logs from your local machine and matches them to git commits and file changes that occur during those sessions. Each vibe coding session appears as a cluster of events on your timeline — the conversation, the resulting commits, and any file modifications.
Is vibe coding billable work?
Absolutely. Vibe coding produces real, production code. The fact that AI helped write it doesn't change the value delivered. Scribe gives you timestamped evidence of every session so you can bill with confidence and show clients exactly when work happened.
Which AI coding tools does Scribe support?
Scribe parses Claude Code conversation logs natively. For other tools like Cursor, Copilot, and Windsurf, Scribe captures the git commits and file changes they produce. Any code that touches your git history or file system is tracked automatically.
Does Scribe read my AI conversations?
Scribe reads the local JSONL log files that Claude Code stores on your machine. It extracts timestamps and message previews to build your timeline. All processing happens locally — no conversation content is sent anywhere. Your vibe coding sessions stay private.
Get more like this
Developer insights and product updates.
Start tracking your vibe coding
Download Scribe and turn AI pair programming into documented, billable work. Free for individuals. No credit card required.