Worklog for Claude Code
Your Claude Code work, written down for you: what you did each day, how long it took, and what it used.
A free, open-source Claude Code usage tracker and daily work log: tokens and hours per project, a timesheet, and plain-language summaries of what you did, across all your Claude accounts and computers. It runs on your computer and keeps your data in your own private git repo.
What you get
Every day
- ✍️ What you worked on, project by project, in plain words. Claude writes it with your own account.
- 📍 Where you left off: your last projects, open tasks, PRs and tickets.
- ✏️ Wrong project? Fix it in two clicks, and Worklog remembers.
Every week
- 🧾 A timesheet with hours, kind of work and one line per project. Download it for Excel or as CSV.
- 📈 Trends compared with last week, in plain sentences, plus goals for hours and tokens.
- 🔎 Ask your worklog: "When did I review PR 505?"
Anywhere
- 📱 On your phone through the GitHub app, from a summary in your private data repo.
- 🖼️ A card to share your week. It shows totals only, never prompts or files.
- 👥 Several Claude accounts and computers, even with one-click account switchers.
🔒 Private: everything stays on your computer and in your own private git repo. 💻 Runs on Linux, macOS and Windows. ⚡ Light and fast.
Try it (nothing is installed)
pipx run --spec worklog-for-claude-code claude-worklog demo
Open http://localhost:8766 to look around with made-up data. Press Ctrl+C to stop.
Install in 3 steps
You need Python 3.10+, git and Claude Code. No pipx yet? See the beginner guide.
1. Install
pipx install worklog-for-claude-code
2. Create a folder for your log and start Worklog
git init ~/claude-worklog-data # Windows PowerShell: git init "$HOME\claude-worklog-data"
claude-worklog install-service
3. Open http://worklog.localhost:8765 (or http://localhost:8765) and fill in the short form.
A checklist shows anything still missing, with the exact command for your computer, and disappears when everything is ticked. Then just use Claude Code as usual.
A closer look
Every project, in plain words, with tasks and PRs. |
Goals and where you left off, at the top of Today. |
Trends, compared with last week. |
Ask your worklog anything about past work. |
A timesheet, ready for Excel. |
A card to share your week. |
Privacy and trust
- Only short notes are saved: the first 300 characters of your prompts, token counts, file names and commit messages. Never your files or Claude's replies.
- Common secrets (API keys, passwords, e-mails) are blanked out before saving. This is best effort, so keep your data repo private.
- Summaries and "Ask Claude" use your own Claude account. Turn AI off in Settings to stay fully offline.
- The only other request: once a day, Worklog asks pypi.org whether a new version is out. Nothing about you is sent, and you can turn it off.
- It's a personal log, not a performance score. Hours are your active time with Claude, not a measure of your output.
- Every release is built and signed by GitHub, and checked on Linux, macOS and Windows before it's published. Verify a release →
Questions
Can I see it on my phone? Yes. Turn on Settings → On your phone on one computer, then open your data repo's phone folder in the GitHub app. It stays private.
Wrong project on a card? Click ✏️ Edit to rename it or move the sessions. Worklog can remember the folder you always start in.
Several accounts, computers or GitHub accounts? Settings walks you through it. Test connection shows which GitHub account your computer signs in as. See Full setup.
It says Sonnet, but I use Opus? The "By model" list shows what Claude Code really used. For better summaries, pick Opus in Settings → Summaries.
How do I update? Click Update now when the dashboard says a new version is out (it checks every 2 hours; Check for updates at the bottom of the page asks right away). From a terminal: pipx upgrade --pip-args=--no-cache-dir worklog-for-claude-code, then click Restart now on the page. (Still the old version?)
Something isn't working? Run claude-worklog doctor, or see Troubleshooting.
How do I remove it? claude-worklog uninstall-service, then pipx uninstall worklog-for-claude-code. Your log stays.
Like it? ⭐
If Worklog saves you time, please star it on GitHub. It helps others find it.
📘 Beginner guide · 📖 Full guide · 🐛 Report a bug · 📝 Changelog
MIT © 2026 Urvin · Not affiliated with or endorsed by Anthropic.
Metadata
Release files for worklog-for-claude-code 0.5.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| worklog_for_claude_code-0.5.2.tar.gz | 249.8 kB | With provenance | Details for worklog_for_claude_code-0.5.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| worklog_for_claude_code-0.5.2-py3-none-any.whl | Python 3 | none | any | Details for worklog_for_claude_code-0.5.2-py3-none-any.whl |
Total release size: 454.6 kB
Release files / worklog_for_claude_code-0.5.2.tar.gz
| Download URL | worklog_for_claude_code-0.5.2.tar.gz |
|---|---|
| Size | 249.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d4d8e6d5090a2cf3115d5285767d7796bbac9de529c2ff8f1a79e08d312ace26
|
|
BLAKE2b-256 checksum How to use checksums |
808bc0b7d9d6d6452590d5301f563731fcaee7ee0b27daa77a322c4197f45d88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / worklog_for_claude_code-0.5.2-py3-none-any.whl
| Download URL | worklog_for_claude_code-0.5.2-py3-none-any.whl |
|---|---|
| Size | 204.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d20d54094908229551abb4f2c3d86b909b76998f74ee6d81cddbd1ba98854d56
|
|
BLAKE2b-256 checksum How to use checksums |
4499f0261918b8745cd2a03b9028ca114107bb574d87c02d53428c3e288a1ca9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logSecurity for worklog-for-claude-code 0.5.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for worklog_for_claude_code-0.5.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.