Fetching from the wire…
01
02
03
04
05
06
07
08
Tools2026-06-18 · source-backed
They work at different layers. RTK sits between the agent and the shell, compressing per-command output 60-90% across 100-plus commands. Headroom sits as a local API proxy compressing everything bound for the model: JSON, AST-aware code, logs, RAG results, conversation history. Run both and you strip noise at the source and again before the API call. Given the GitHub-load and AI-COGS stories above, token discipline isn't optional anymore. (Andrew Patterson)
Each link below shares sources, entities, or timing with this story.
headroom benchmarked against Squad / Shared entities / Shared topic / What happened next
Linked by a graph relationship (headroom benchmarked against Squad); both cover AST, GitHub, Headroom, JSON; overlapping topics (ast-aware, code, headroom).
headroom uses LLM / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (headroom uses LLM); both cover AST, GitHub, JSON, RAG; overlapping topics (agent, between, code).
headroom uses LLM / Shared entities / Shared topic / What happened next
Linked by a graph relationship (headroom uses LLM); both cover AST, GitHub, Headroom, JSON; overlapping topics (agent, between, headroom).
RTK supports Claude Code / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (RTK supports Claude Code); both cover GitHub, Headroom, RAG; overlapping topics (call, code, headroom, token).
headroom uses LLM / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (headroom uses LLM); both cover GitHub, RTK; overlapping topics (bill, code, token).
RTK supports Cursor / Shared entities / Shared topic / What happened next
Linked by a graph relationship (RTK supports Cursor); both cover GitHub, JSON; overlapping topics (agent, code).
headroom uses LLM / Shared entity: GitHub / Shared topic / What happened next / Tension
Linked by a graph relationship (headroom uses LLM); both cover GitHub; overlapping topics (agent, code, token).
RTK supports Cursor / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (RTK supports Cursor); both cover GitHub, RTK; overlapping topics (code, token).