Your commits prove your work.
Screenshots don't.
WebWork takes screenshots to prove you were at your computer. Scribe reads what you actually shipped — git commits, file changes, and AI coding sessions — and turns that into invoices your clients can trust.
Side by side
Surveillance-based monitoring vs. output-based evidence.
| Feature | Scribe | WebWork |
|---|---|---|
| How it proves work | Git commits, diffs, file changes, and AI session logs | Periodic screenshots and keystroke/mouse activity counts |
| AI coding tool tracking | Parses Claude Code, Cursor, Copilot, Gemini, Codex, and more | |
| Simultaneous & automated work | Captures parallel agent sessions and automated/background runs as overlapping evidence — built for running several AI agents at once | Single active timer per person — surveils one screen, can't represent parallel or automated work |
| Primary audience | Individual developers and freelancers billing clients | Team managers monitoring remote employee productivity |
| Invoicing | Built-in, generated from your tracked timeline | Invoicing available via integrations |
| Privacy | Local SQLite — nothing leaves your machine by default | Screenshots and activity data sent to WebWork servers |
| Retroactive history | Reads existing git repos — years of history from day one | Only from when monitoring was installed and running |
| Setup | Download app, point at your project folders | Install desktop agent, configure screenshot intervals |
| Evidence granularity | Commit-level: what changed, when, across which files | Time blocks and activity scores during screenshot intervals |
| Works without being at the keyboard | Yes — commits and file saves are captured asynchronously | No — inactivity periods are flagged or excluded |
| Pricing | Free / $12/mo Pro | $4.99–11.99/user/mo |
Which tool fits?
Stick with WebWork if you
- Manage a remote team and need verifiable attendance records
- Work in a context where screenshot proof is contractually required
- Need shift scheduling, payroll, and leave management in one tool
- Require GPS tracking or geofencing for field employees
Switch to Scribe if you
- Freelance and want billing evidence from your actual code output
- Use AI coding tools and want those sessions captured as billable work
- Refuse to run screenshot software on your development machine
- Want retroactive history from your existing git repos
- Need invoices generated directly from your work timeline
Common questions
How is Scribe different from WebWork?
WebWork is a workforce monitoring platform built for managers overseeing remote teams — it uses screenshots and activity scores to prove presence at a computer. Scribe is built for individual developers and freelancers who need to prove what they actually built: git commits, file changes, and AI coding sessions. Scribe generates invoices directly from that evidence; WebWork requires integrations for invoicing.
Why is git evidence better than screenshots for billing?
A screenshot shows you were at your keyboard. A git commit shows exactly what you shipped, when, and in which files. Clients who understand code find commit-based timelines far more credible and precise than screenshot galleries. Scribe can link specific commits directly to invoice line items.
Does Scribe capture AI coding tool sessions like WebWork cannot?
Yes. Scribe reads the conversation logs that Claude Code, Cursor, GitHub Copilot, Gemini, Codex, and others store locally. It extracts session timelines and adds them as work evidence — showing not just that an AI tool was open, but what coding work happened inside those sessions. WebWork has no awareness of AI coding tool sessions.
Is my data private with Scribe?
Everything is stored in a local SQLite database on your machine. No screenshots, no keystroke logs, no activity data leaves your machine unless you explicitly sync to a team hub. WebWork sends screenshots and activity data to their servers by design.
Can I use Scribe as a freelancer working for clients who require time tracking?
Yes. Scribe exports your timeline as a verifiable record of work — commit hashes, file change counts, timestamps, and AI session summaries — that you can attach to invoices. If a client specifically requires screenshot proof, Scribe does not provide that and WebWork or a similar monitoring tool would be needed instead.
Scribe is in private beta
We're rolling out access gradually. Join the waitlist and we'll notify you when your seat opens.
Get more like this
Developer insights and product updates.