Kronumos vs RTK (Rust Token Killer): Shell Output Filter vs Full Rust Coding Harness
Both tools are written in Rust to stop AI coding agents from wasting tokens on noisy CLI output—but they operate at very different layers of your workflow.
What RTK (Rust Token Killer) Does Well
RTK (Rust Token Killer) is a focused, lightweight Rust CLI proxy that sits in front of shell commands (such as `git`, `ls`, or test runners) and compresses verbose stdout before another coding agent reads it. If you only want a tiny command-output filter while keeping a separate third-party agent untouched, RTK solves that single layer cleanly.
Where Kronumos Goes Beyond Output Filtering
Compressing stdout reduces prompt bloat, but token waste is only half of why autonomous coding sessions fail. Agents still write broken syntax, accidentally leak `.env` credentials into prompts, mutate shared exported symbols without updating callers, and leave dirty diffs in git when tests fail.
Kronumos combines sub-millisecond Rust log surgery (-91.3% trace noise) with a complete deterministic engineering harness:
- Zero-LLM Tree-sitter AST Auditing (`/hunt` & `/blast`) across Rust, Python, TypeScript/TSX, JavaScript, and Go.
- Auto Blast-Radius Guard: warns and gates edits on `HIGH`/`CRITICAL` shared symbols until downstream callers are audited.
- In-Memory Secret Shield (<0.01ms) + strict `.env` / private key exclusion before any prompt leaves your machine.
- Transactional Test Verification + Auto-Rollback + Proof-of-Fix Verification Receipts (terminal, JSON, and PR Markdown).
- Cross-Session Knowledge Crystals (SQLite) + embedded VidyaX gas-metered bytecode VM (`vxvm` / `110 KB` WASM).
- Multi-backend freedom: Kronumos Cloud, OpenRouter BYOK, local offline Ollama, and native Windows PowerShell without WSL.
Which One Should You Pick?
Choose **RTK** if you strictly want a minimal shell-output compressor in front of an existing single-vendor CLI. Choose **Kronumos** if you want local Rust token reduction integrated directly with Tree-sitter AST safety, secret masking, test-verified auto-rollback, BYOK/Ollama routing, and native Windows/Linux/macOS execution.
“Output filtering saves tokens; combining output filtering with Tree-sitter AST blast guards, secret masking, and transactional test rollbacks makes autonomous coding safe.”
Frequently Asked Questions
Is Kronumos only a CLI output filter like RTK?
No. Kronumos includes local Rust log surgery (-91.3% trace noise) alongside a full autonomous terminal coding agent, 0-LLM Tree-sitter AST auditing, blast-radius protection, and test-verified auto-rollback.
Can I run Kronumos static checks without using any LLM tokens?
Yes. Both `kronumos hunt .` and `kronumos blast` run 100% locally via embedded Tree-sitter grammars in milliseconds with zero LLM API calls.
Audit your repository in milliseconds with zero LLM calls
Run native Rust Tree-sitter AST checks on Linux, macOS, and Windows PowerShell, or test in the browser.