linguo2625469/workbuddy2api-panel

Project Overview

WorkBuddy2API Panel is a self-hosted reverse-proxy gateway that exposes Tencent CodeBuddy accounts through an OpenAI-compatible /v1/chat/completions endpoint. It obtains credentials via OAuth device authorization, manages a pool of accounts with rotation, cooldowns and circuit breakers, keeps sessions sticky across turns, and ships an embedded web panel for account operations, usage stats and configuration.

It is built as an enhanced fork of Sliverkiss/workbuddy2api and targets individuals who want a local OpenAI-style entry point for their own accounts. The gateway also automates CodeBuddy growth tasks: the panel can complete 17 of the 18 growth tasks through API calls, including the event chains and reward claims, without the official client.

The project is marked unmaintained as of 2026-10-21. The README states that upstream is tightening detection of non-official clients, that the author has limited time, and that resold/packaged versions are widespread.

Getting Started

The recommended server path is Docker Compose:

git clone https://github.com/linguo2625469/workbuddy2api-panel.git
cd workbuddy2api-panel
cp config.example.json config.json
docker compose up -d --build
curl -s http://localhost:7863/healthz

A health response looks like {"healthy":0,"total":0,"service":"workbuddy2api"}; it returns 503 when no usable account exists. Then open http://localhost:7863/panel/, click Add Account, complete the OAuth login in the browser, and the credential is written and hot-loaded into the pool.

Alternatives: run the prebuilt GHCR image with docker run, run the wb2api.exe single-file binary on Windows, or build from source (go run ./cmd/server -config config.json). The command-line login.sh flow is Linux/macOS only and requires bash plus python3.

After adding an account, verify with GET /v1/models and a chat request to /v1/chat/completions using the configured api_key.

Usage Constraints

• Non-official upstream. All traffic goes to CodeBuddy's private/reverse-engineered endpoints; the README warns that upstream may block non-official clients and that account risk is borne by the user. It restricts use to your own authorized accounts in a local/private environment.
• Credentials are plaintext. auths/*.json contains access and refresh tokens. Keep it out of git and restrict permissions.
• No TLS and optional auth. When api_key is empty, the API and panel are open; a public deployment needs a key and ideally a reverse proxy.
• Regional variants and enterprise accounts behave differently. Enterprise accounts do not have the personal growth system, so check-in, travel and task features are skipped for them.
• Windows binary. The README offers a self-contained .exe built from source; the repository itself states it ships no prebuilt Release.

HotRepo's take

The repository recorded 4,799 stars and 1,721 forks in a Go language monthly snapshot dated 2026-11-12, with 2,239 stars gained that month; no GitHub overall daily rank or star-curve samples are available here. The large fork count beside the usage notice is consistent with the README's own complaint about third-party repackaging and resale. The maintainer has also disclosed that much of the recent issue/PR handling and code work was AI-assisted and that the project stopped maintenance in October 2026, so the practical value now is mainly as a self-hosted personal tool that no longer tracks upstream protocol changes.