docs/guide/index.md
RTK is a CLI proxy that sits between your AI assistant and your development tools. It filters command output before it reaches the LLM, keeping only what matters and discarding boilerplate, progress bars, and noise.
Result: up to 90% fewer bash output bytes reaching the LLM per command, without changing how you work. You run git status as usual — RTK's hook intercepts it, filters the output, and the LLM sees a compact 3-line summary instead of 40 lines.
Your AI assistant runs: git status
↓
Hook intercepts (PreToolUse)
↓
rtk git status (transparent rewrite)
↓
Raw output: 40 lines → Filtered: 3 lines
↓
LLM sees the compact output
Zero config changes to your workflow. The hook handles everything automatically.
RTK reduces bash output bytes — the output a shell command sends back before your agent reads it. That is not the same as reducing your bill by the same amount.
Bash output is one contributor to input tokens, alongside your prompt, the system prompt and conversation history. Input tokens are in turn only part of the bill, which also counts output tokens. The reduction dilutes at every step.
See How RTK Savings Work for the full picture, including why the token counts RTK reports are estimates.
Dozens of commands across all major ecosystems — Git, Cargo/Rust, JavaScript, Python, Go, Ruby, .NET, Docker/Kubernetes, and more. See What RTK Optimizes for the full list with per-command bash output reduction.
rtk gain # total savings across all sessions
rtk gain --daily # day-by-day breakdown
rtk gain --weekly # weekly aggregation
See Token Savings Analytics for export formats and analysis workflows.
rtk discover # find commands that ran without RTK (missed savings)
rtk session # RTK adoption rate per Claude Code session
See Discover and Session for details.