Summary
When the same physical repository is available both as a native Windows folder (e.g. C:\repos\<name>) and as a WSL path (wsl.localhost/<Distro>/home/<user>/src/<name>), hoosage registers them as two completely separate projects with different IDs, instead of recognizing them as the same codebase.
Why this happens
Project identity is derived from a hash of the full workspace URI (per the project's own documentation on project attribution). A native file:// URI and a vscode-remote://wsl+... URI for the same on-disk content necessarily hash differently.
Impact
- Usage/cost history for a single project gets split across two entries in the dashboard, undercounting real per-project cost and making comparisons misleading.
- Users switching between opening a repo natively vs. via WSL (e.g. for different tooling needs) will see fragmented, confusing history.
Suggested improvement
- At minimum, document this limitation prominently in the dashboard UI (not only in the README) when two projects with a similar folder name are detected.
- Consider an optional "merge projects" action so users can manually combine history for projects they know are the same repository accessed through different roots.
Summary
When the same physical repository is available both as a native Windows folder (e.g.
C:\repos\<name>) and as a WSL path (wsl.localhost/<Distro>/home/<user>/src/<name>), hoosage registers them as two completely separate projects with different IDs, instead of recognizing them as the same codebase.Why this happens
Project identity is derived from a hash of the full workspace URI (per the project's own documentation on project attribution). A native
file://URI and avscode-remote://wsl+...URI for the same on-disk content necessarily hash differently.Impact
Suggested improvement