workbuddy2api-panel
把腾讯WorkBuddy账号变成 OpenAI 兼容 API 的多账号网关，同时自动完成任务中心全部任务，附 Web 管理面板（账号池可视化 / 积分任务 / 配置热更新）。基于 Sliverkiss/workbuddy2api 的增强分支
Runs with mockssource: GitHubGoMITcommit 1e23c2b27bec
Go, MIT licensed. The project labels itself: admin panel, codebuddy, gateway, golang, openai api, reverse proxy and workbuddy.
workbuddy2api-panel runs, with stand-ins for the services it depends on. An Argusic agent installed it in 26 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
WorkBuddy2API server v1.11.11-panel prebuilt binary launches, serves OpenAI-compatible model catalog (39 models), management panel, and auth. Loads 2 mock accounts but needs real CodeBuddy credentials for upstream chat.
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 92 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.
- V compiler does not support .go extension (golang backend removed)20 minutes
- Real CodeBuddy OAuth credentials required for upstream API calls5 minutes
- Install time
- 26 minutes
- Cold machine to finish
- 27 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- wb2api binary launched on :7863; curl healthz returned healthy:2; curl /v1/models returned 39 models; curl /status returned 2 healthy accounts; curl /panel/ returned 200; curl with wrong key returned 401
- Model tokens used
- 180,681
- Exact commit tested
- 1e23c2b27bec
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
}
print('ARGUSIC_RESULT:' + json.dumps(result))
\"" in /work/repo
succeeded in 0ms:
2026-10-05T13:43:16.360214Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-05T13:43:16.360394Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-05T13:43:16.360429Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-05T13:43:16.360449Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-05T13:43:16.360460Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-05T13:43:16.360569Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
tokens used
180,681Replay 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 26 minutes.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 | 1/3 | Runs with mocks | 92.00 | 0.49 |
Topics (from GitHub)
admin-panelcodebuddygatewaygolangopenai-apireverse-proxyworkbuddy
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/workbuddy2api-panel)Questions
- Does workbuddy2api-panel run?
- workbuddy2api-panel runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 26 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test workbuddy2api-panel?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1e23c2b27bec. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test workbuddy2api-panel?
- The run that produced this verdict cost $0.49: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does workbuddy2api-panel take to install?
- 26 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-panel need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing workbuddy2api-panel?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for workbuddy2api-panel?
- 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.