mirrord

Run any process, on your machine or in an AI agent's environment, as if it were a pod in your Kubernetes cluster: real env vars, DNS, network, traffic.

Runssource: GitHubhomepageRustMITcommit 6c5955a3cefc

Rust, MIT licensed. The project labels itself: agent skills, ai agents, ai coding, api, backend, claude code, cli and cloud.

mirrord runs. An Argusic agent installed it in 25 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

mirrord CLI binary and layer build, run, and pass all unit tests and clippy checks on x86_64 Linux with nightly-2026-08-13 Rust toolchain.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.10 (measured)
recorded runs
3
last tested
stars
5,336
forks
217
open issues
73
watchers
22
size
65 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing mirrord, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • libclang.so not found (needed by bindgen for frida-gum-sys)5 minutes
  • Out of disk space (40GB overlay, 24GB in target/) during workspace test run3 minutes
  • bindgen failed: stddef.h not found (clang missing include paths)2 minutes
  • Rust toolchain not installed1 minute
  • protoc compiler not found (needed by containerd-client build dependency)1 minute
  • MIRRORD_LAYER_FILE env var not defined at compile time1 minute
Install time
25 minutes
Cold machine to finish
30 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
Model tokens used
163,244
Exact commit tested
6c5955a3cefc
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

How the result was proved
runs before 2026-09-07 did not record the command used to check the result
Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

  [BINARY_ARGS]...
          Arguments to pass to the binary
Options:
  -t, --target <TARGET>
          Name of the target to mirror.
          Valid formats: - `targetless` - `pod/{pod-name}[/container/{container-name}]` - `deployme…
          E.g `pod/my-pod/container/my-container`.
  -n, --target-namespace <TARGET_NAMESPACE>
Everything works. Let me now produce the final result.
tokens used
163,244
Everything works. Let me now produce the final result.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 3 times, so the result is not a one-off.

What did not, or is not known

  • Took 25 minutes to install, slower than the median of the 8 comparable projects Argusic has measured.

Of the 9 agent-skills projects Argusic has installed and timed, mirrord was the 8th fastest to reach a running state, and 8 of 9 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.10
Argusic Runner1/3Ran out of time0.000.16
Argusic Runner1/3Ran out of time0.000.17

Topics (from GitHub)

agent-skillsai-agentsai-codingapibackendclaude-codeclicloudcloud-nativedebugdeveloper-toolsdevelopmentdevopsdevtoolidejetbrainskubernetesrusttrafficvscode

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/mirrord.svg)](https://argusic.com/subject/mirrord)

Questions

Does mirrord run?
Yes. mirrord runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test mirrord?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6c5955a3cefc. 3 attempts are recorded, and the full method is on the methodology page.
What did it cost to test mirrord?
The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does mirrord take to install?
25 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does mirrord need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing mirrord?
6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does mirrord compare with the alternatives?
Of the 9 agent-skills projects Argusic has installed and timed, mirrord was the 8th fastest to reach a running state, and 8 of 9 reached one at all.
Where is the evidence for mirrord?
All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion