radar runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 21 minutes, hitting 3 errors on the way, and recorded the session.

How did Argusic test radar?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 74ddfa9b88a0. 3 attempts are recorded, and the full method is on the methodology page.

What did it cost to test radar?

The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does radar take to install?

21 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 radar need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing radar?

3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for radar?

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.

radar

The missing open-source Kubernetes UI with a built-in MCP server for AI agents. See what's broken, why, and what changed. Issues, Topology, event timeline, Helm, GitOps, live service traffic, and cluster audits - all in one Go binary.

Runs with mockssource: GitHub homepageGoApache-2.0commit 74ddfa9b88a0

Go, Apache-2.0 licensed. The project labels itself: ai agents, argocd, cloud native, fluxcd, gitops, helm, k8s and kubectl plugin.

radar runs, with stand-ins for the services it depends on. An Argusic agent installed it in 21 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Radar builds from source and runs; frontend is built and embedded, Go binary serves the UI at localhost:9282, and all unit tests pass.
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 92 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs with mocks
Argusic Score: 92 / 100
cost of the verifying run: $0.12 (measured)
recorded runs: 3
last tested: 2026-09-05
stars: 3,447
forks: 217
open issues: 92
watchers: 12
size: 73 MB
created: 2026-01-20
last push: 2026-09-23

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-23. 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 radar, 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.

Go not installed (required Go 1.26+)2 minutes
Node.js v18.19.1 is too old (project requires >=20)2 minutes
Timeline test TestSQLiteStore_StartCleanupLoop_PrunesByMaxSizeWithoutRetention had a race/deadline of 2s that was too short1 minute

Install time: 21 minutes
Cold machine to finish: 21 minutes
Errors hit and fixed: 3 hit, 3 fixed with no human help
Model tokens used: 343,393
Exact commit tested: 74ddfa9b88a0
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
Behaviour against real services: this run was verified against stand-in services only

The end of the recording

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

2026/09/05 20:41:26 "GET http://localhost:9282/ HTTP/1.1" from 127.0.0.1:54830 - 200 1623B in 79.41…
200
The app serves the UI at HTTP 200. Everything works. Let me compute the elapsed minutes and write t…
Start time: ~20:20 (from the session start). Let me check
exec
/bin/sh -lc 'echo "Start: 20:20 -- End: $(date +%H:%M)"' in /work/repo
 succeeded in 0ms:
Start: 20:20 -- End: 20:41
About 21 minutes elapsed. Let me produce the final report.
tokens used
343,393
About 21 minutes elapsed. Let me produce the final report.

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

Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
Licensed Apache-2.0, as reported by its host.
Measured 3 times, so the result is not a one-off.

What did not, or is not known

Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Took 21 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.

Of the 12 ai-agents projects Argusic has installed and timed, radar was the 11th fastest to reach a running state, and 8 of 12 reached one at all.

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 by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs with mocks	92.00	0.12	2026-09-05 20:41 UTC
Argusic Runner	2/3	Ran out of time	0.00	0.05	2026-09-03 18:21 UTC
Argusic Runner	1/3	Ran out of time	0.00	0.09	2026-09-03 17:11 UTC

Embed the badge

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

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

Questions

Does radar run?: radar runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 21 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test radar?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 74ddfa9b88a0. 3 attempts are recorded, and the full method is on the methodology page.
What did it cost to test radar?: The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does radar take to install?: 21 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 radar need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing radar?: 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does radar compare with the alternatives?: Of the 12 ai-agents projects Argusic has installed and timed, radar was the 11th fastest to reach a running state, and 8 of 12 reached one at all.
Where is the evidence for radar?: 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.