workbuddy2api-hub

WorkBuddy 国际国内多账号反代网关,支持 Codex / Claude Code / DSH与标准 OpenAI 客户端。

Runssource: GitHubhomepagePythonMITcommit fa787e828e1a

Python, MIT licensed. The project labels itself: api gateway, claude code, codebuddy, codex, deepseek, openai api, reverse proxy and tencent.

workbuddy2api-hub runs. An Argusic agent installed it in 0.1 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

The server starts, listens on the configured port, serves the web dashboard (HTTP 200), returns health status via GET /health, and all 20 bundled test suites pass cleanly.

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.02 (measured)
recorded runs
2
last tested
stars
3,971
forks
972
open issues
8
watchers
5
size
15 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.

Install time
under a minute
Cold machine to finish
1 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
python3 tests/run_all.py exited 0, 20 passed 0 failed 0 skipped; curl -s http://127.0.0.1:18789/health returned HTTP 200 with valid JSON
Model tokens used
31,531
Exact commit tested
fa787e828e1a
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.

  --line:#e2e8f0; --line-hover:#cbd5e1;
  --fg:#0f172a; --dim:#64748b; --dim-light:#94a3b8;
  --accent:#2563eb; --accent-hover:#1d4ed8; --accent-soft:rgba(37,99,235,.08);
  --accent2:#16a34a; --accent2-soft:rgba(22,163,74,.1);
  --warn:#d97706;
Everything works. Let me compile the final results.
exec
/bin/sh -lc 'cd /work/repo && kill %1 2>/dev/null; sleep 1; echo "done"' in /work/repo
 succeeded in 856ms:
done
tokens used
31,531

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 0.1 minutes, faster than the median of the 31 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 32 api-gateway projects Argusic has installed and timed, workbuddy2api-hub was the 3rd fastest to reach a running state, and 22 of 32 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 0.1 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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 Runner2/3Runs100.000.02
Argusic Runner1/3Runs100.000.01

Topics (from GitHub)

api-gatewayclaude-codecodebuddycodexdeepseekopenai-apireverse-proxytencentvibe-codingworkbuddyworkbuddy2api

Embed the badge

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

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

Questions

Does workbuddy2api-hub run?
Yes. workbuddy2api-hub runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test workbuddy2api-hub?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit fa787e828e1a. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test workbuddy2api-hub?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does workbuddy2api-hub take to install?
0.1 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 workbuddy2api-hub need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing workbuddy2api-hub?
Nothing did, in the recorded run: zero errors between clone and running.
How does workbuddy2api-hub compare with the alternatives?
Of the 32 api-gateway projects Argusic has installed and timed, workbuddy2api-hub was the 3rd fastest to reach a running state, and 22 of 32 reached one at all.
Where is the evidence for workbuddy2api-hub?
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.

Discussion