Release notes

FEATURE

Parallel working copies of the same project no longer fracture your usage stats

When you use worktrees (a Git feature that lets you check out multiple parallel copies of the same project) to fix bugs or build features, the system finally knows how to consolidate the bill. Previously, it would split the usage from your main folder and your copies into separate projects, cluttering your leaderboards; it now intelligently groups all that usage under the main project's name. If you notice some project totals suddenly merging and growing upon upgrading, this is completely expected. It's like handing out supplementary credit cards to your family: instead of receiving a confusing pile of separate statements, everything is now cleanly rolled up into one master bill, making it immediately clear how much was spent in total.

Original changelog

Original changelogParallel working copies of the same project no longer fracture your usage stats
**git worktree entries collapse into the main project**: running Claude Code or Codex inside a worktree (a duplicate working tree of the same repo) no longer splits `usage` and `usage-fix-bug` into two separate rows in the HTML report and TUI ranking. They are now grouped under the main worktree's directory name. A new `project_resolver.py` module (stdlib only, 3-second timeout, falls back to the previous basename behavior when git is unavailable) is shared by `history_loader.py` and `codex_loader.py`. Seeing historical totals merge on first upgrade is the intended behavior.