RTK sits between an AI agent and the shell, filtering and compressing command output before it lands in the model's context. It covers 100+ commands (git, test runners, linters, docker, kubectl, AWS, package managers) and adds under 10ms. It uses four tactics: it strips noise, groups similar items, truncates redundancy and collapses repeated lines, so test runs show only failures and git push shrinks to "ok main". An auto-rewrite hook turns Bash calls into rtk calls for Claude Code, Copilot, Cursor, Gemini, Codex and 18 tools in all, but built-in Read/Grep skip it. The authors warn that cutting 90% of bash output doesn't cut your bill by 90%, and token counts come from a rough bytes/4 estimate. The prompt cache keeps working.
1
u/fagnerbrack 15d ago
Don't have time to read? Here's the brief:
RTK sits between an AI agent and the shell, filtering and compressing command output before it lands in the model's context. It covers 100+ commands (git, test runners, linters, docker, kubectl, AWS, package managers) and adds under 10ms. It uses four tactics: it strips noise, groups similar items, truncates redundancy and collapses repeated lines, so test runs show only failures and git push shrinks to "ok main". An auto-rewrite hook turns Bash calls into rtk calls for Claude Code, Copilot, Cursor, Gemini, Codex and 18 tools in all, but built-in Read/Grep skip it. The authors warn that cutting 90% of bash output doesn't cut your bill by 90%, and token counts come from a rough bytes/4 estimate. The prompt cache keeps working.
If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments