higress
🤖 AI Gateway | AI Native API Gateway
Could not verifysource: GitHubhomepageGoApache-2.0commit 22368f1e7a28
Go, Apache-2.0 licensed. The project labels itself: ai gateway, ai native, api gateway, cloud native and envoy.
Argusic could not get higress running. An Argusic agent installed it in 13 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Go controller binary and hgctl CLI build and respond to help; all Go unit tests pass (26 packages); WASM AssemblyScript SDK builds both debug and release wasm binaries
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 80 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.
- external/ directories not set up (prebuild)3 minutes
- Go 1.26 not installed in container1 minute
- Git submodules not initialized1 minute
- Install time
- 13 minutes
- Cold machine to finish
- 15 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- go test ./cmd/... ./pkg/... passed 17 packages; hgctl go test ./... passed 9 packages; higress --help prints usage; hgctl --help prints usage; wasm-assemblyscript asbuild produced debug.wasm+release.wasm
- Model tokens used
- 253,322
- Exact commit tested
- 22368f1e7a28
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
253,322 Here are the final results of the full verification run. **What was done:** - Downloaded and installed Go 1.26.0 (not present in the container) - Initialized all 7 git submodules (`istio/api`, `istio/istio`, `istio/client-go`, `istio/pkg`, `is… - Ran `prebuild.sh` which symlinked submodules into `external/` and ran `go mod tidy` - Built the **higress controller** binary (`/tmp/out/higress`, 114MB, responds to `--help` and `ver… - Built the **hgctl CLI** binary (`/tmp/hgctl`, 202MB, responds to `--help`) - Ran **all Go unit tests** across the main repo: **17 packages passed**, 0 failures - Ran **all Go unit tests** for `hgctl`: **9 packages passed**, 0 failures - Built **wasm-assemblyscript** plugins: `npm ci` + `npm run asbuild` produced `debug.wasm` (45KB) … - Could not build wasm-go plugins (requires TinyGo, not available), could not run e2e tests (requir…
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
- Installed in 13 minutes.
- 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 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
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 | 2/3 | Unverified | 80.00 | 0.06 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.13 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/higress)Questions
- Does higress run?
- Argusic could not verify that higress runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test higress?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 22368f1e7a28. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test higress?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does higress take to install?
- 13 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 higress need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing higress?
- 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 higress?
- All 2 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.