The archive · Developer & Business Tools · Product decision · 2026
rtk bets CLI noise is the real cost of AI coding — 67k stars
Rust Token Killer: a CLI proxy that compresses command output before it reaches an AI agent's context, cutting token use 60–90% — 67K stars by end Q2 2026.
rtk
What the business is
rtk (Rust Token Killer) is an open-source CLI proxy that intercepts shell commands, compresses their output before it enters an AI coding agent's context window, and logs token savings per command.
How it started
rtk was built in Rust by a French developer (Patrick Szymkowiak per the project's own git history) as a single-binary, zero-dependency tool. ROSS Index Q1 2026 logged it at 15.7K stars by 2026-03-31, with the company founded in Lyon, France in 2026.
What happened
By end Q2 2026 rtk hit 67.0K stars (ROSS), with support for 16 AI coding tools through auto-rewrite hooks — Claude Code, Cursor, Codex, Gemini CLI, Copilot, Cline, OpenCode, Hermes, Pi and more — plus 100+ commands and an RTK Pro team tier. Korben's May 2026 review reported a git diff dropping from 12,000 to 960 tokens (−92%) and a 12-file refactor from 74,700 to 6,960 tokens; the reviewer measured 81.5% savings.
How it ended up
Still live and open source (Apache 2.0): the official site showed 78.1K stars in September 2026, and RTK Pro offers team-level token savings, security and governance.
Background
rtk (Rust Token Killer) is an open-source CLI proxy written in Rust: it intercepts shell commands, compresses their output before it lands in an AI coding agent's context window, and logs per-command token savings. A single binary with zero dependencies, it rewrites everyday commands like git status into rtk git status through hooks for Claude Code, Cursor, Codex, Gemini CLI, Copilot and more, applying boilerplate filtering, similar-line grouping, smart truncation and deduplication.
The bet is that the real cost of AI-assisted coding is not the model but the noise an agent reads — every cargo test, npm build or git log dumps boilerplate into a 200K-token window, crowding out reasoning, shortening sessions and inflating per-token bills. rtk attacks the noise at the source instead of asking developers to change prompts or habits. Korben's May 2026 review measured a git diff falling from 12,000 to 960 tokens (−92%) and a 12-file refactor from 74,700 to 6,960 tokens, with roughly 70% savings over a full workday.
Growth followed the metric. ROSS Index Q1 2026 logged rtk at 15.7K stars by 2026-03-31; Q2 2026 showed 67.0K stars by 2026-06-30, a 50.9x quarterly jump, and the official site displayed 78.1K stars by September 2026. The site's public dashboard reports one developer saving 138M tokens across 15,720 commands, and RTK Pro extends the tool to teams with governance.
What has to be true
- It targets a metered, measurable pain — tokens — so value is visible in rtk gain the day it is installed.
- Working at the hook layer means zero habit change: the agent's commands are rewritten transparently, which removes the adoption barrier.
- Compressing output improves signal-to-noise for the model, so savings compound into better reasoning, not just lower bills.
- A single Rust binary with no dependencies keeps install friction near zero across macOS, Linux and Windows.
- The Pro tier gives a natural path from viral open-source tool to team product without breaking the free tool.
What can be applied
Charge where the pain is metered: when users pay per token, removing context noise is worth real money even though the model stays the same — optimize the metered resource, not the feature.
Aftermath
As of September 2, 2026, rtk is live and open source under Apache 2.0 with the official site showing 78.1K stars. It supports 16 AI coding tools via auto-rewrite hooks, ships prebuilt binaries for macOS, Linux and Windows, and offers RTK Pro (pro.rtk-ai.app) for team-level token savings, security and governance. ROSS Index Q2 2026 lists rtk as a Lyon, France startup founded in 2026 at 67.0K stars. Open questions: whether token savings hold up outside power-user workflows, and whether a CLI proxy can grow into a durable company rather than a developer utility.
Sources
spotted an error? The archive wants to know.
Your turn
You just read one. Describe what you are building, and see who is betting on the same thing.
Free account · 3 free questions · no card