Skip to main content

work-ledger

tests

work-ledger turns one person's local Claude Code transcripts into attributable usage, recurring-work trends, and evidence for improving how they work. It is a reader, not session instrumentation or a team observability platform.

flowchart LR
    A["Local Claude Code transcripts"] --> B["Attributable work<br/>cost, tokens, tools, chapters"]
    B --> C["Trends and recurring initiatives"]
    C --> D["Evidence-backed action"]

Today, the strongest surfaces show what happened: live usage, costs, activity, chapters, timelines, trends, rollups, and repeated-work signals. Recommendations are an early Tell layer. Do automation is deliberately not presented as mature or automatic.

Install

Published package:

python3 -m pip install --user work-ledger

Inside an active virtual environment, omit --user.

The commands below need work-ledger 0.2.0 or newer; work-ledger about reports the version you actually have. If you end up on something older, install from a source checkout instead — uv or pipx is the smoother path, since python3 -m venv fails on a stock Ubuntu box without python3-venv installed:

git clone https://github.com/dhk/work-ledger.git
cd work-ledger && uv venv && uv pip install -e .

Reviewed convenience installer:

curl -fsSL https://raw.githubusercontent.com/dhk/work-ledger/main/scripts/install.sh | bash

Read scripts/install.sh before running it. For a careful isolated source install, extras, upgrades, and troubleshooting, see INSTALL.md.

Start here

work-ledger --once            # current session usage
work-ledger activity          # attribute work by kind/tool/skill
work-ledger chapters          # group work into initiatives (hosted by default)
work-ledger timeline          # practice over time
work-ledger trend             # cost over time
work-ledger --help

The complete CLI reference, including reports, rollups, recommendations, patterns, limits, and export, lives in docs/commands.md. For running work-ledger's local web UI or connecting it to Claude itself via MCP, see docs/commands.md and INSTALL.md respectively. The documentation index separates shipped truth from research and proposals.

Privacy and network boundary

Transcript parsing, cost calculation, activity, recommendations, deterministic rollups, exports, reports, and the read-only web UI run locally. export only writes a local file.

There are exactly five network paths in the adopted architecture:

  1. chapters sends prompt and unit snippets to Anthropic's hosted Haiku API by default, using your credentials.
  2. The optional Ollama chapter backend sends those snippets to a separately running server, localhost by default.
  3. After patterns enable and backend configuration, anonymous recommended/used counters can go to your personal pattern backend.
  4. With that same opt-in plus a findings token, explicit MCP findings submission sends review text to the personal backend.
  5. WORK_LEDGER_ROLLUP_MATCHING=semantic opts rollup into sending unmatched initiative titles to hosted Haiku.
flowchart LR
    subgraph Machine["Your machine"]
        T["Claude Code transcripts"] --> W["work-ledger"]
        W --> F["Local files, cache, SQLite, reports"]
        W --> UI["127.0.0.1 web UI"]
        W -. "optional chaptering" .-> O["Ollama server"]
    end
    W -. "default chapters: snippets<br/>optional semantic rollup: titles" .-> A["Anthropic API"]
    W -. "opt-in counters<br/>explicit findings text" .-> P["Personal pattern backend"]

Failures in optional calls degrade to local results; they do not block the core views. The exhaustive, authoritative list and persisted-data model are in docs/architecture.md.

Scope and maturity

work-ledger is for an individual inspecting their own usage. It is not a team/org governance product, and the optional pattern backend remains personal-only and self-hosted. Cost estimates use a hardcoded pricing table and should be treated as estimates; Claude subscription limit thresholds are calibrated approximations.

See PRODUCT_BRIEF.md for product boundaries, ROADMAP.md for maturity, and CONTRIBUTING.md to make changes.

License

MIT — see LICENSE.

Metadata

Release files for work-ledger 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for work-ledger 0.2.0
File Size Uploaded
work_ledger-0.2.0.tar.gz 211.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for work-ledger 0.2.0
File Interpreter ABI Platform
work_ledger-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 364.1 kB

Release files / work_ledger-0.2.0.tar.gz

Download URL work_ledger-0.2.0.tar.gz
Size 211.6 kB
Tags Source
SHA-256 checksum
How to use checksums
3ba136fb91ae7cac4e5e076964a30f60767961a85510882a6f4dc8f2b56e6e32
BLAKE2b-256 checksum
How to use checksums
037f744d1839eac5897eb37bf960d04c78538daa3b59ccbc642327268dc31206
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 14, 2026.

Transparency log

Release files / work_ledger-0.2.0-py3-none-any.whl

Download URL work_ledger-0.2.0-py3-none-any.whl
Size 152.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f18fcbdc33e92417da052feb1302e68b0753f9c9c41ea502a86a035e523471a0
BLAKE2b-256 checksum
How to use checksums
6fc6eade8c4ddfd9c1c5abd7e0f3856f5613d73b2c45c5a56ea43ab0c6883e73
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 14, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.0 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page