Your git history is
your timesheet
WakaTime watches your editor. getScribe reads your git commits, file changes, and Claude Code conversations — then turns them into invoices. No plugins to install. No data sent to the cloud.
Side by side
Different tools, different philosophies.
| Feature | getScribe | WakaTime |
|---|---|---|
| Git commit tracking | Commits, diffs, and complexity-based time estimation | Branch detection only |
| File change tracking | Filesystem-level scanning across all projects | Editor file events only |
| AI conversation tracking | Claude Code sessions parsed from local logs | |
| Invoicing | Generate invoices from your timeline | |
| Where your data lives | Local SQLite on your machine | WakaTime cloud servers |
| Free tier history | 30 days | 7 days |
| Setup | Download app, point at folders | Install a plugin in each editor |
| Works across editors | Yes — tracks git, not your editor | Yes — via 40+ separate plugins |
| Offline | Full functionality, always | Queues events until online |
| Pricing | Free / $12/mo Pro | Free (1 week) / $9–14/mo |
Which tool fits?
Stick with WakaTime if you
- Want real-time per-file coding metrics in your editor
- Use coding leaderboards or public developer profiles
- Need language and framework breakdowns by project
- Have a separate invoicing tool you already like
Switch to getScribe if you
- Bill clients and need invoices from your tracked work
- Want your data on your machine, not in the cloud
- Pair program with Claude Code or other AI tools
- Use multiple editors, terminals, and workflows
- Need more than 7 days of history without paying
Common questions
How is getScribe different from WakaTime?
WakaTime tracks coding activity through editor plugins — time spent in files, languages, and branches. getScribe takes a different approach: it scans your git history, file system, and Claude Code conversations to build a timeline of work evidence. getScribe also includes invoicing, runs locally, and doesn't require editor plugins.
Does getScribe work with my editor?
getScribe is editor-agnostic. It tracks your work through git commits and file changes, not editor events. Vim, Emacs, VS Code, JetBrains, nano — it doesn't matter.
Can getScribe replace WakaTime?
If you want time tracking tied to invoicing and privacy, yes. If you rely on WakaTime's per-file activity breakdowns or real-time coding metrics within your editor, that's a different use case. Some developers use both.
Is my data private?
getScribe stores everything in a local SQLite database. No code, conversation content, or activity data leaves your machine unless you explicitly sync to a team hub.
See your work timeline in minutes
Download getScribe, point it at your project folders, and watch your commit history turn into a timeline. No account required.
Get more like this
Developer insights and product updates.