Repository navigation
RTK Commands
You almost never invoke rtk directly in normal use — the hook rewrites Bash commands for you transparently. The commands below are the meta commands you'd type yourself for analytics, debugging, or hook management.
Show cumulative token-savings analytics across all sessions.
rtk gainSample output (shape, not exact format):
Total commands proxied: 1,284
Tokens saved: 1,372,440
Estimated cost saved: $5.49
Top filtered commands: git status, flutter build, melos run
Same metrics, plus a per-command history.
rtk gain --historyUseful when you want to see which commands actually triggered RTK in recent sessions — handy debugging step when you're not sure the hook is firing.
Scan your Claude Code transcript history for commands that RTK could have filtered but didn't (because RTK wasn't active yet, or the binary was missing).
rtk discoverTreat the output as a hint list of commands worth keeping under the RTK umbrella.
Register RTK's hook globally (writes to ~/.claude/settings.json). One-time, idempotent — safe to run again.
Display the current hook state. Authoritative source for "is RTK active?" — preferred over checking files manually.
Remove the global hook. The binary stays installed.
Run a command through RTK's filter without going through Claude Code's hook rewrite. Useful when you want to see exactly what RTK would return to Claude for a given command.
rtk proxy git status
rtk proxy flutter build apkIf rtk proxy git status returns something sensible but Claude still sees the unfiltered output, the issue is in the hook, not in RTK's filtering.
Self-explanatory. Always include this in any bug report.
- rtk-ai/rtk — upstream source & release notes.
coming soon
coming soon