同一個專案的平行副本,用量不再被拆得七零八落
當你用工作樹(worktree,讓同一個專案多開幾份平行副本的 Git 功能)來修 bug 或開發新功能時,系統終於懂得把帳算在一起了。以前它會把你主資料夾跟副本資料夾的用量拆成兩個獨立專案,導致你的用量排行榜看起來很亂;現在它會自動把這些副本的用量,全部算在主專案頭上。升級後如果你看到某些專案的數字突然變大、名次合體,這是正常的。就像你拿了幾張附卡給家人刷,以前帳單會分開好幾份寄來讓你眼花,現在全部彙整到主卡帳單裡,一眼就能看出總共花了多少。
發布日期:2026-05-27
當你用工作樹(worktree,讓同一個專案多開幾份平行副本的 Git 功能)來修 bug 或開發新功能時,系統終於懂得把帳算在一起了。以前它會把你主資料夾跟副本資料夾的用量拆成兩個獨立專案,導致你的用量排行榜看起來很亂;現在它會自動把這些副本的用量,全部算在主專案頭上。升級後如果你看到某些專案的數字突然變大、名次合體,這是正常的。就像你拿了幾張附卡給家人刷,以前帳單會分開好幾份寄來讓你眼花,現在全部彙整到主卡帳單裡,一眼就能看出總共花了多少。
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.
**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.