openchoreo
OpenChoreo is an internal developer platform for Kubernetes
Runssource: GitHubhomepageGoApache-2.0commit 1aeed89856d0
Go, Apache-2.0 licensed. The project labels itself: ai agents, ci cd, cncf, developer platform, devops, gitops, internal developer platform and kubernetes.
openchoreo runs. An Argusic agent installed it in 38 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
OpenChoreo 1.3.0 compiles, all 9 binaries build, all Go unit tests pass, and all Python agent test suites pass inside the container.
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
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go 1.26.3 not found in container; project requires Go 1.26.x2 minutes
- Corrupted google.golang.org/protobuf module cache (NUL bytes in desc_validate.go) causing all Go packages importing protobuf to fail build2 minutes
- setup-envtest kubebuilder assets missing; controller tests hanging indefinitely2 minutes
- uv (Python package manager) not installed; Python agent tests cannot run without it1 minute
- Install time
- 38 minutes
- Cold machine to finish
- 44 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- go build -o /tmp/manager,occ,openchoreo-api,observer,event-forwarder,cluster-gateway,cluster-agent,remote-agent,remote-agent-router succeeded for all 9 binaries; go test -count=1 -timeout=120s ./... (excluding e2e) passed all packages (0 FAIL); uv run --group dev pytest -q passed in all 3 Python agents
- Model tokens used
- 234,210
- Exact commit tested
- 1aeed89856d0
- 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.
- 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.
Go Version: go1.26.3 linux/amd64 Server: <not connected> === ? github.com/openchoreo/openchoreo/pkg/hash [no test files] ok github.com/openchoreo/openchoreo/pkg/mcp 0.129s ok github.com/openchoreo/openchoreo/pkg/mcp/mcpaudit 0.012s ok github.com/openchoreo/openchoreo/pkg/mcp/tools 0.571s ? github.com/openchoreo/openchoreo/pkg/observability [no test files] All tests pass with zero failures across the board. Here's my final assessment: tokens used 234,210 All tests pass with zero failures across the board. Here's my final assessment:
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 4 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 38 minutes to install, slower than the median of the 42 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 43 ai-agents projects Argusic has installed and timed, openchoreo was the 40th fastest to reach a running state, and 32 of 43 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
Topics (from GitHub)
ai-agentsci-cdcncfdeveloper-platformdevopsgitopsinternal-developer-platformkubernetesmcpobservabilityplatform-engineering
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openchoreo)Questions
- Does openchoreo run?
- Yes. openchoreo runs. Argusic installed and launched it on a clean machine in 38 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test openchoreo?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1aeed89856d0. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test openchoreo?
- The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does openchoreo take to install?
- 38 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 openchoreo need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing openchoreo?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does openchoreo compare with the alternatives?
- Of the 43 ai-agents projects Argusic has installed and timed, openchoreo was the 40th fastest to reach a running state, and 32 of 43 reached one at all.
- Where is the evidence for openchoreo?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.