The Token Compression Illusion: Why I'm Skeptical of RTK
RTK promises dramatic token savings for coding agents, but raw terminal compression is not the same as cheaper, safer, or more accurate software engineering.
Backend engineer with 13+ years in production systems. Currently building AI-powered tools for prediction markets, running a self-hosted homelab that probably has too many containers, and finishing an MSc in AI. Currently into: system engineering, 0-1, LLMs, self-hosting, and whatever I’m figuring out this week because of the rabbit hole I got into.





RTK promises dramatic token savings for coding agents, but raw terminal compression is not the same as cheaper, safer, or more accurate software engineering.
Part 1 of a structural critique of Rails in 2026: the magic that made Rails dominant also became an architectural cage for the stateful, real-time web.
Ten requests from an agent to the codebase it works in — local reasoning, visible boundaries, one way of doing things. None of them are new. All of them matter more now.
Most self-hosted *arr compose files are ticking time bombs: flat networks, fake kill switches, no health checks. Here is how I built one that actually holds up.