Proof of Work
The Work Session Logger — Merkle-chained command records, QR verification, and client-ready reports.
The Work Session Logger turns a terminal session into a tamper-evident record of billable work.
How it works
- Record — toggle Start Work Log from the menu; you're asked for a Client and Project, and a pulsing indicator shows in the status bar. Every command is captured with timestamp, directory, and duration. An interrupted session resumes on next launch.
- Chain — each entry's hash is
SHA-256(timestamp | command | directory | prev_hash), chained from genesis; on stop, a binary SHA-256 Merkle tree over all entry hashes produces the session root. Editing any entry breaks verification. - Report — export a professional HTML report (opens in your browser) or copy as Markdown for pasting into an invoice or email. The report groups time by tool — Claude Code, Codex, Aider, Docker, Terraform, kubectl, Helm, AWS/GCloud, Git, npm, Cargo, pip, AntBot, and more — with per-tool duration and counts.
- Verify — the summary carries a QR code encoding the session metadata and Merkle root; scanning it verifies the record wasn't modified.
What it proves — and what it doesn't
The chain proves integrity: these commands ran, at these times, for these durations, and nobody edited the record afterwards. It does not certify the quality of the work — it's a notary, not a reviewer.
Who it's for
Consultants and freelancers who invoice by the hour and want to hand clients something better than a hand-typed timesheet. A day of agent-assisted work exports as a verifiable worksheet in seconds.
Privacy
Session logs are local files on your machine. Nothing is uploaded anywhere; you choose what to export and share.