mirrord Now Strips Cache-Control From Every Response It Proxies — Because Browsers Were Caching Agent-Redirected Traffic

GitHub·medium signalXBlueskyLinkedInCopy link

metalbear-co/mirrord (5,255 stars) shipped 3.246.0 on 2026-08-10. The agent now rewrites HTTP response `Cache-Control` headers to `no-cache, no-store, must-revalidate` so browsers and caching proxies don't retain responses served while mirrord is redirecting a target (disable via the new `agent.override_cache_control`), and `target.path.labels` can now intercept every matching pod in a namespace from one local session (operator required). The repo also rewrote its own description this cycle to 'Run any process, on your machine or in an AI agent's environment, as if it were a pod in your Kubernetes cluster' — a six-year-old dev-tool repositioning around agent execution environments.