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 13 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The WorkBuddy2API panel server builds and runs in the container, serving the management panel at /panel/ and OpenAI-compatible API endpoints at /v1/chat/completions and /v1/models; all 18 Go test suites pass.

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

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
2
last tested
stars
4,934
forks
1,777
open issues
13
watchers
6
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.

Time lost to each failure while testing workbuddy2api-panel, 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.

  • Go 1.22.5 not found in container2 minutes
Install time
13 minutes
Cold machine to finish
3 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
go test ./... -count=1 -timeout 120s passed all 18 packages (0 failures); curl http://127.0.0.1:7863/panel/ returned 200; curl -H 'Authorization: Bearer test_key' http://127.0.0.1:7863/v1/models returned 200; /tmp/wb2api --help and the server binary version confirmed launch; /tmp/login and /tmp/credit binaries also built and ran.
Model tokens used
57,795
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.

ok    github.com/linguo2625469/workbuddy2api-panel/internal/prompt  0.003s
ok    github.com/linguo2625469/workbuddy2api-panel/internal/redisstore  0.004s
ok    github.com/linguo2625469/workbuddy2api-panel/internal/scheduler  0.306s
ok    github.com/linguo2625469/workbuddy2api-panel/internal/server  8.910s
ok    github.com/linguo2625469/workbuddy2api-panel/internal/session  0.045s
ok    github.com/linguo2625469/workbuddy2api-panel/internal/upstream  0.448s
ok    github.com/linguo2625469/workbuddy2api-panel/internal/usage  0.002s
All builds, tests, and endpoints verified. Here's the final report:
2026-11-08T01:20:51.234357Z ERROR codex_core::session: failed to record rollout items: thread 01a1b…
tokens used
57,795
All builds, tests, and endpoints verified. Here's the final 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

  • Installed in 13 minutes.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

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.

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/3Runs with mocks92.000.01
Argusic Runner1/3Runs with mocks92.000.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.

[![Tested by Argusic](https://argusic.com/badge/workbuddy2api-panel.svg)](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 13 minutes, hitting 1 error 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. 2 attempts are 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.01: 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?
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 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?
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.
Where is the evidence for workbuddy2api-panel?
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