oh-my-cpa

Self-hosted control plane & usage observability console for CLIProxyAPI (CPA), AI providers, client keys, streaming telemetry, and model cost snapshots.

Runssource: GitHubhomepageTypeScriptMITcommit 671dfe51c6e3

TypeScript, MIT licensed. The project labels itself: ai gateway, cliproxyapi, cpa, dashboard, golang, llm, observability and proxy.

oh-my-cpa runs. An Argusic agent installed it in 15.8 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The binary builds, all Go packages test pass, the full frontend builds and embeds, the app serves the SPA and health endpoint with status ok in both demo mode (in-process fixture) and non-demo mode (with a mock CPA answering the v8 API probe).

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.16 (measured)
recorded runs
1
last tested
stars
274
forks
23
open issues
3
watchers
1
size
72 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 oh-my-cpa, 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.

  • Node.js is v18.19.1, requires v22.23.22.5 minutes
  • Go 1.27.1 not in PATH; go binary absent2 minutes
  • pnpm not found1 minute
  • 2 repository-test failures in maintenance/weekly lanes (fuzz and advisory)
Install time
16 minutes
Cold machine to finish
16 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
pnpm verify (type-check + logic tests + vitest + lint) passed; pnpm check-docs passed; go test ./... passed 30/30 packages; ./bin/oh-my-cpa launched and 'curl -fsS http://127.0.0.1:8080/omc/api/healthz' returned {"cpa_connected":true,"cpa_management_api":"v8","database_status":"ok","status":"ok","version":"v0.1.0-dev"} in both demo and non-demo modes; SPA served HTTP 200 on /omc/
Model tokens used
950,445
Exact commit tested
671dfe51c6e3
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.

1793109931
Now let me compile everything into the final result
exec
/bin/sh -lc 'echo "Start: $(date -d @1793108995)"; echo "Now: $(date +%s) = $(date)"; echo "Diff: $…
 succeeded in 0ms:
Start: Tue Oct 27 13:49:55 UTC 2026
Now: 1793109940 = Tue Oct 27 14:05:40 UTC 2026
Diff: 945 seconds
Here's the complete report.
tokens used
950,445
Here's the complete 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

  • 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 MIT, as reported by its host.

What did not, or is not known

  • Took 15.8 minutes to install, slower than the median of the 20 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 21 ai-gateway projects Argusic has installed and timed, oh-my-cpa was the 13th fastest to reach a running state, and 15 of 21 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 Runner1/3Runs100.000.16

Topics (from GitHub)

ai-gatewaycliproxyapicpadashboardgolangllmobservabilityproxyreactself-hostedsqlitetelemetry

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/oh-my-cpa.svg)](https://argusic.com/subject/oh-my-cpa)

Questions

Does oh-my-cpa run?
Yes. oh-my-cpa runs. Argusic installed and launched it on a clean machine in 16 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test oh-my-cpa?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 671dfe51c6e3. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test oh-my-cpa?
The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does oh-my-cpa take to install?
15.8 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 oh-my-cpa need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing oh-my-cpa?
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 oh-my-cpa compare with the alternatives?
Of the 21 ai-gateway projects Argusic has installed and timed, oh-my-cpa was the 13th fastest to reach a running state, and 15 of 21 reached one at all.
Where is the evidence for oh-my-cpa?
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