What problem does this solve?
We need to support WSL dual-install path resolution and token count aggregation for Kiro (both Kiro IDE and Kiro CLI). Currently, TokenTracker cannot discover Kiro installations in WSL or native dual setups.
Proposed solution
- Wire Kiro through the standard
resolveInstallPaths and multiInstallParse patterns.
- Map the Kiro CLI SQLite database path at
~/Library/Application Support/kiro-cli/data.sqlite3.
- Allow the
both mode to scan and merge logs from both environments natively.
- Namespace cursors under
native and wsl inside the configuration.
- Update the
tracker status and tracker doctor commands to display all resolved installations.
Category
New AI tool integration
What problem does this solve?
We need to support WSL dual-install path resolution and token count aggregation for Kiro (both Kiro IDE and Kiro CLI). Currently, TokenTracker cannot discover Kiro installations in WSL or native dual setups.
Proposed solution
resolveInstallPathsandmultiInstallParsepatterns.~/Library/Application Support/kiro-cli/data.sqlite3.bothmode to scan and merge logs from both environments natively.nativeandwslinside the configuration.tracker statusandtracker doctorcommands to display all resolved installations.Category
New AI tool integration