by metalbear-co
Run local code as if it were a pod in a remote Kubernetes cluster: real env vars, DNS, network, traffic. Used by AI coding agents and developers.
# Add to your Claude Code skills
git clone https://github.com/metalbear-co/mirrordLast scanned: 5/12/2026
{
"issues": [
{
"type": "npm-audit",
"message": "@vitest/mocker: Vulnerability found",
"severity": "medium"
},
{
"type": "npm-audit",
"message": "esbuild: esbuild enables any website to send any requests to the development server and read the response",
"severity": "medium"
},
{
"type": "npm-audit",
"message": "vite: Vite Vulnerable to Path Traversal in Optimized Deps `.map` Handling",
"severity": "medium"
},
{
"type": "npm-audit",
"message": "vite-node: Vulnerability found",
"severity": "medium"
},
{
"type": "npm-audit",
"message": "vitest: Vulnerability found",
"severity": "medium"
}
],
"status": "PASSED",
"scannedAt": "2026-05-12T06:37:44.932Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": true
}mirrord lets developers and AI coding agents run local processes in the context of their Kubernetes environment. It’s meant to provide the benefits of running your service on a cloud environment (e.g. staging) without actually going through the hassle of deploying it there, and without disrupting the environment by deploying untested code. It comes as a Visual Studio Code extension, an IntelliJ plugin and a CLI tool. You can read more about it here.
Adopted by: monday.com, SurveyMonkey, Cadence, CoLab, Daylight Security, Zooplus, and others.
No comments yet. Be the first to share your thoughts!
mirrord uses your machine's default kubeconfig for access to the Kubernetes API.
You can use either
brew install metalbear-co/mirrord/mirrord
or
curl -fsSL https://raw.githubusercontent.com/metalbear-co/mirrord/main/scripts/install.sh | bash
or using Nix (not official, community maintained):
# Using nix-env (legacy)
nix-env -iA nixpkgs.mirrord
# Using nix profile (recommended)
nix profile install nixpkgs#mirrord
or on Windows using Chocolatey:
choco install --pre mirrord
mirrord exec <process command> --target <target-path>
e.g.
mirrord exec node app.js --target pod/my-pod
When you select a pod to impersonate, mirrord launches a pod on the same node as the pod you selected. The new pod is then used to connect your local process and the impersonated pod: it mirrors incoming traffic from the pod to your process, routes outgoing traffic from your process through the pod, and does the same for file reads, file writes, and environment variables. You can read more about it here.
Container run inside the pod launched by mirrord requires additional Linux capabilities:
CAP_NET_ADMIN and CAP_NET_RAW - for modifying routing tablesCAP_SYS_PTRACE - for reading target pod environmentCAP_SYS_ADMIN - for joining target pod network namespaceHowever, you can disable any subset of those in the configuration. This will possibly limit mirrord functionalities or even make it unusable in some setups.
MIRRORD_AGENT_DISABLED_CAPABILITIES=CAP_NET_RAW,CAP_SYS_PTRACE mirrord exec node app.js --target pod/my-pod
mirrord works first-class with Claude Code, Cursor, Codex CLI, Gemini CLI, and other AI coding agents, letting them run and verify generated code against real cluster services without deploying.
For setup guides and ready-made workflow skills, see metalbear-co/skills or the mirrord for AI Agents page.
Our FAQ is available here. If you have a question that's not on there, feel free to ask in our Discussions or on Slack.
Contributions are very welcome. Start by checking out our open issues, and by going through our contributing guide. We're available on Slack for any questions.
Join our Slack for questions, support and fun.
We always appreciate hearing how mirrord has made a difference for our users.
Check out our ADOPTERS.md to see how others are using mirrord —
and open a pull request to add your organization if you’d like to share how mirrord has been useful to you.
We take our community seriously and we are dedicated to providing a safe and welcoming environment for everyone. Please take a few minutes to review our Code of Conduct.