Turning Tencent CodeBuddy Into an OpenAI API—And Grinding Its Quests for You

What it does

WorkBuddy2API Panel is an enhanced fork of a Go reverse proxy that wraps Tencent CodeBuddy behind an OpenAI-compatible /v1/chat/completions endpoint. It pools multiple accounts, refreshes OAuth tokens, and routes around rate limits with circuit breakers and cooling timers. A built-in web panel handles browser-based OAuth, hot-reloads configuration changes, and visualizes account health without external frontend dependencies.

The interesting bit

The project reverse-engineers CodeBuddy’s client telemetry to automate 17 of 18 “growth tasks,” mimicking desktop, web, and mini-program fingerprints to report fake progress and claim rewards. Only a charity task requiring a verified donation receipt remains out of reach.

Key highlights

• Weighted random account selection with session stickiness—even deriving a sticky key from the first message hash when clients omit conversation_id.
• Automated daily check-ins, back-to-school events, and growth-task grinding that reportedly yields ~1,950 credits and 78 energy per fresh account without touching the official client.
• Embedded web UI compiled into the single Go binary, supporting live config edits, dark/light themes, and log filtering by task, chat, or system channels.
• Outbound request fingerprint scrubbing and system-prompt replacement to reduce content-moderation false positives.

Caveats

• Explicitly unofficial and self-described as “private testing only”; upstream breaking changes or policy enforcement could brick the automation at any time.
• One growth task (Expert_Philanthropy) is impossible to fake because the server validates a real donation receipt.
• Task automation depends on replaying precise telemetry signatures across multiple client platforms, which are inherently brittle against upstream updates.

Verdict

Worth deploying if you already hold multiple CodeBuddy accounts and want a standard OpenAI client interface that passively farms credits. Avoid if you need vendor-backed stability or worry about terms-of-service ambiguity.