CPA-Manager-Plus

A self-hosted CPA / CLIProxyAPI management panel and AI gateway observability dashboard for requests, usage, cost, quota, failures, and account health.

Runssource: GitHubhomepageGoMITcommit eea422fd6a19

Go, MIT licensed. The project labels itself: ai gateway, claude code, cliproxyapi, codex, cost analysis, cpa, gateway monitoring and observability.

CPA-Manager-Plus runs. An Argusic agent installed it in 3 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

CPA Manager Plus web app installs, builds, type-checks, and runs all 4156 web tests passing; repo-level tests pass 256/257. The dev server serves the management panel on port 5173 and returns HTTP 200.

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.04 (measured)
recorded runs
1
last tested
stars
3,696
forks
390
open issues
38
watchers
4
size
37 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 CPA-Manager-Plus, 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.

  • System Node.js v18.19.1 is too old (project requires ^20.19.0 or >=22.12.0)2 minutes
Install time
3 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
npm run test:web passed 4156/4156; npm run test:repo passed 256/257 (1 expected x origin/main); npm run build succeeded; dev server returned HTTP 200
Model tokens used
112,256
Exact commit tested
eea422fd6a19
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.

- `npm run dev` — **Vite dev server started** on localhost:5173, returned **HTTP 200**
tokens used
112,256
Everything works. Let me compile the final report.
Here's what I did and verified:
**Install**: Downloaded Node.js v22.12.0 (system Node v18.19.1 was too old), ran `npm install` — su…
**Verification**:
- `npm run test:web` — **4156 passed, 252 test files** across the web app
- `npm run test:repo` — **256 passed, 1 expected failure** (the failing test requires `origin/main`…
- `npm run type-check` — **0 errors**, TypeScript compiles cleanly
- `npm run build` — **built** `dist/index.html` (6,410.65 kB)
- `npm run dev` — **Vite dev server started** on localhost:5173, returned **HTTP 200**

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.
  • Installed in 3 minutes, faster than the median of the 5 comparable projects Argusic has measured.
  • Recovered from all 1 error 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.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 6 ai-gateway projects Argusic has installed and timed, CPA-Manager-Plus was the 1st fastest to reach a running state, and 5 of 6 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.
  • A quick evaluation: it was running 3 minutes after the clone.

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 Runner1/3Runs100.000.04

Topics (from GitHub)

ai-gatewayclaude-codecliproxyapicodexcost-analysiscpagateway-monitoringobservabilityopenaiopenai-compatiblequota-managementrequest-monitoringusage-tracking

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/CPA-Manager-Plus.svg)](https://argusic.com/subject/cpa-manager-plus)

Questions

Does CPA-Manager-Plus run?
Yes. CPA-Manager-Plus runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test CPA-Manager-Plus?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit eea422fd6a19. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test CPA-Manager-Plus?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does CPA-Manager-Plus take to install?
3 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 CPA-Manager-Plus need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing CPA-Manager-Plus?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does CPA-Manager-Plus compare with the alternatives?
Of the 6 ai-gateway projects Argusic has installed and timed, CPA-Manager-Plus was the 1st fastest to reach a running state, and 5 of 6 reached one at all.
Where is the evidence for CPA-Manager-Plus?
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.

Discussion