Workfold

Workfold folds local Git and filesystem timestamps onto one representative Monday-to-Sunday week. It highlights activity outside your intended working hours without pretending that timestamped events are hours worked.

Workfold is local, private by design, terminal-only, and currently alpha.

Install

pip install workfold
workfold --help

For an isolated installation, use uv tool install workfold or pipx install workfold. Standalone binaries are available from GitHub releases.

Quick start

Run workfold inside a Git repository to see the current ISO week:

workfold

The four selectors you will use most are:

workfold . -t 2w3d                    # rolling elapsed window
workfold . -t 2026-W31                # one ISO week
workfold . -m fs                      # current filesystem metadata
workfold . -m both -p full -t all     # exhaustive local view
workfold . -m git -p portable -t all  # evidence stored in Git objects
workfold . -e git:tag:tagger fs:file:modified

They control separate parts of the request:

The profiles answer different questions:

• standard: What does the ordinary activity pattern look like?
• portable: What dated evidence is stored inside Git objects?
• full: What can this machine still discover for the selected mode and time?

For exact control, -e/--events accepts identifiers such as git:commit:author, git:tag:tagger, and fs:file:modified; quote wildcards such as 'git:*'. -l/--list appends bounded event details. Paths must appear before either space-separated selector, or after an option-terminating --.

Schedules support daily intervals, breaks, overnight shifts, and all:

workfold . --hours 'Mo-Thu 08:00-16:30; Fr 08:00-14:00'
workfold . --hours 'Mo-Fr 22:00-06:00'
workfold . --hours all

See the usage guide for clustering, fixed bands, identity markers, day hiding, grids, exact event selection, configuration, and every CLI option.

Configuration

Put personal defaults in the platform configuration directory, or project defaults in workfold.toml:

timezone = "Europe/Berlin"
hours = "Mo-Thu 08:00-16:30; Fr 08:00-14:00"
mode = "git"
profile = "portable"
cluster-anchor = "midnight"
band-label = "start"
show-empty-bands = true
grid = "vertical"
hide-empty-days = ["weekend"]

Python projects may use [tool.workfold] in pyproject.toml instead. Values resolve as built-in → global → nearest project → CLI. Inspect the result and each value's origin without collecting timestamps:

workfold . --show-config

Use --config FILE for one exact file or --no-config for built-ins plus CLI only. The usage guide documents locations, discovery, merging, and every supported key.

Reading the chart

• Circles are Git events; squares are filesystem events.
• Green/blue and filled markers are inside the schedule; red and hollow markers are outside. Colorless output preserves the shape distinction.
• One symbol is one event; busy cells use exact ×N counts.
• Empty time is compressed, and ⋮ reports a meaningful gap.
• Identity-marker mode replaces Git circles with codes mapped in the key.

The summary independently splits all events by schedule and by calendar day. Weekend events can therefore also be outside working hours.

Accuracy and privacy

• Events are discrete timestamp observations, not work sessions or duration.
• Collection is local: Workfold does not contact a Git host or telemetry service.
• Git history can be rewritten; reflogs can expire; filesystem metadata is a mutable snapshot and birth time depends on platform and filesystem support.
• Coverage reports unavailable, unsupported, and unreadable evidence that can prevent a complete answer. Known timestamps outside the requested time or identity scope are not counted as coverage outcomes.

See the documentation for every CLI option, collector semantics, coverage guarantees, and platform notes.

Development

The Python package lives directly in workfold/; there is no src/ wrapper.

nix develop
uv sync --locked --extra dev
uv run --locked pytest
uv run --locked ruff check .
uv run --locked ruff format --check .
uv run --locked pyright

Use nix run .#docs-dev for the documentation site and nix run .#docs-check to validate it. The architecture guide documents the package boundaries, dependency rules, data pipeline, and test layout.