RTK, the CLI tool that made my terminal quieter

Some tools scream for attention. RTK does the opposite: it makes terminal output smaller before it lands in my LLM context. That's exactly why I like it.

RTK stands for Rust Token Killer and lives here: github.com/rtk-ai/rtk. It is a small, fast CLI tool that runs commands like git status, grep, find, cat, test runs or build output through a filter. Not to hide information, but to cut the noise.

What RTK actually does

The idea is simple. Instead of every dev command dumping full, often page-long output into an agent context, RTK sits in front and returns a compact version: status, relevant files, errors, diffs, summaries. The rest gets dropped.

The project aims for 60 to 90 percent lower token consumption, supports more than 100 commands and ships as a single Rust binary that is fast enough to not feel like an extra layer.

What I find useful in practice:

• rtk git status shows repository state without the Git novel.
• rtk git diff condenses diffs to the relevant parts.
• rtk grep groups search results better than a raw wall of text.
• rtk read can read files more compactly when an agent only needs orientation.
• rtk test <cmd> or test-specific wrappers show mostly failures instead of success noise.

Why this fits agents especially well

I work a lot with coding agents. They are powerful, but they eat context. Raw terminal output is often absurdly wasteful there: 200 lines when only three matter. RTK sits exactly at that point and turns "here is everything" into "here is what you probably need".

It has integrations and hooks for several agent setups, including Claude Code, Codex, Cursor, Windsurf, Pi and others. You can also just call RTK directly in front of commands.

What it isn't

RTK is not a substitute for understanding and not a magical "makes everything faster" layer. If I need the complete output, I want the complete output. If a tool needs raw debugging, I skip RTK.

But for everyday use, this unassuming kind of tool is gold: less noise, less token waste, less scrolling.

Who it's worth it for

Anyone who lives in the terminal and works with LLMs or coding agents. If you regularly throw logs, diffs, search results and test output into an agent context, RTK is one of those tools that disappears after setup. Best compliment.