Back to Rtk

Discover and Session

docs/guide/analytics/discover.md

0.38.02.0 KB
Original Source

Discover and Session

rtk discover — find missed savings

rtk discover analyzes your Claude Code command history to identify commands that ran without RTK filtering and calculates how many tokens you lost.

bash
rtk discover                    # analyze current project history
rtk discover --all              # all projects
rtk discover --all --since 7    # last 7 days, all projects

Example output:

Missed savings analysis (last 7 days)
────────────────────────────────────
Command              Count   Est. lost
cargo test              12     ~48,000 tokens
git log                  8     ~12,000 tokens
pnpm list                3      ~6,000 tokens
────────────────────────────────────
Total missed:           23     ~66,000 tokens

Run `rtk init --global` to capture these automatically.

If commands appear in the missed list after installing RTK, it usually means the hook isn't active for that agent. See Troubleshooting — "Agent not using RTK".

rtk session — adoption tracking

rtk session shows RTK adoption across recent Claude Code sessions: how many shell commands ran through RTK vs. raw.

bash
rtk session

Example output:

Recent sessions (last 10)
─────────────────────────────────────────────────────
Session                         Total   RTK   Coverage
2026-04-06 14:32  (45 cmds)       45    43      95.6%
2026-04-05 09:14  (38 cmds)       38    38     100.0%
2026-04-04 16:50  (52 cmds)       52    49      94.2%
─────────────────────────────────────────────────────
Average coverage: 96.6%

Low coverage on a session usually means RTK was disabled (RTK_DISABLED=1) or the hook wasn't active for a specific subagent.