fix: discover doesn't match /usr/bin/grep as rtk grep equivalent

[FlorianBruniaux]

Bug

rtk discover classifies /usr/bin/grep as an unhandled command instead of mapping it to rtk grep.

Reproduce

Run rtk discover on a session where Claude Code used /usr/bin/grep (full path). It appears in "TOP UNHANDLED COMMANDS" instead of "MISSED SAVINGS" with rtk grep as equivalent.

Real example

/usr/bin/grep    7    /usr/bin/grep -rni "twitch" /Users/chr..

Should be classified as:

/usr/bin/grep    7    rtk grep    existing    ~XXX tokens

Root cause

The discover classifier in src/discover/ likely matches on the command name only (grep), not on absolute paths (/usr/bin/grep, /bin/grep).

Fix

Normalize absolute binary paths before classification. Strip leading path components for well-known binaries:

• /usr/bin/grep → grep
• /bin/ls → ls
• /usr/local/bin/git → git

This affects any command called via full path in Claude Code bash tool calls.

Impact

7 occurrences missed in one session. Likely affects any user on macOS where Claude Code sometimes resolves to full paths.

[pszymkowiak]

wshm · Automated triage by AI

🔍 Automated Triage

🐛 Category	bug
🟡 Priority	medium
🎯 Confidence	92%

Summary

rtk discover fails to match absolute-path binaries (e.g. /usr/bin/grep) to their rtk equivalents; fix by normalizing paths before classification.

💡 This looks like a simple fix that could be auto-resolved. Use /wshm fix to attempt it.

📁 Relevant files

• src/discover/

---

Triaged automatically by wshm · This is an automated analysis, not a human review.

[FlorianBruniaux]

Fixed on develop via commit 8b162fe (release v0.31.0 merge).

The fix is strip_absolute_path() in src/discover/registry.rs line 85-86, with tests at lines 2280-2285. /usr/bin/grep -rn foo correctly classifies as rtk grep equivalent.

Closing.