Replace usage of Claude native tools (grep, read, find, ls) by RTK ?

[alterphp]

Claude seems having its own grep, read, find, ls native tools. Is it really worth it to replace them by RTK filtering OS tools ?

[niklasmarderx]

The key difference is where filtering happens. Claude built-in tools (Read, Grep, etc.) run inside the context window — full output is consumed as tokens before the model decides what to keep. RTK sits before the model, filtering raw command output so fewer tokens enter the context in the first place.

Example: ls -la in a large repo produces ~200 lines. The native Bash tool sends all 200 as tokens. rtk ls strips metadata and compacts it to ~40 lines — roughly 70% fewer tokens that the model never processes.

Where RTK adds less value: tools where Claude already does targeted extraction (like Read with line ranges). But for commands that dump noisy output (git log, cargo test, docker ps), the savings compound quickly across a session.

[aeppling]

Hey for now not possible like we do for Bash tool, but this is in the roadmap to cover more, for now we didn't had the time to look in related PRs because we were focusing on organizing repository, contribution, refactoring, fixing priority issues.

We will get back to this task asap once we've solve main usage issues

[aeppling]

However , RTK context tell claude he should better use rtk commands for token savings, but this is not as effective as a hook usage