WorkBuddy Notes, Verified Fixes, and What This Site Will Not Claim

WorkBuddy is Tencent's AI office workbench, and this guide documents the parts its official pages leave out. Those parts are concrete: the Linux packages no button links to, the permissions a Skill can ask for, and the fixes worth re-checking. Every value here was checked on 2026-11-10 against the vendor's own endpoints. Limits are stated rather than smoothed over.

01 /What does this guide cover that the official docs do not?

The official WorkBuddy documentation describes the happy path well. It explains how to assign a task in natural language, how the assistant plans the steps, and how a finished file appears in a folder you authorised. What it is quiet about is what happens when your platform is not the documented one, when an endpoint returns a field the guide never mentions, or when a packaged extension asks for screen control. These pages are independent notes about those gaps, not a rewrite of the manual.

WorkBuddy is described by Tencent as an all-scenario AI office workbench covering daily office work, code development, and design creativity. In practice, the behaviour that changes how you work is local file access: within directories you authorise, the client edits files directly instead of returning text for you to copy. Scheduled tasks draw on three sources, local, project, and cloud, and the cloud source runs in an isolated Tencent Cloud sandbox without needing your computer to stay online, per the official Automation Guide, checked on 2026-11-10. That split matters later, because the cloud sandbox does not support workspace access, full access, or custom models.

This site is deliberately narrow in scope. It documents verified endpoints, reproduced behaviour, and stated limits, and where the data is missing the page does not exist yet. Nothing here is sponsored, and no page is a ranking or a recommendation slot. For the WorkBuddy feature list itself, the official docs remain the better source, and About WorkBuddy Central records who verifies these pages.

02 /Why is the Linux package missing from the download page?

The official download page covers Windows and macOS with direct installers. For Linux it names only two distributions, UOS and Kylin, and tells users to get the build from the system app store. There is no general .deb or .rpm button anywhere on that page, which is why so many readers conclude that no Linux build exists. That conclusion is wrong, and the difference between "not linked" and "not shipped" is the reason this site exists.

The vendor does build general-purpose .deb and .rpm packages and publishes them through the same update endpoint the desktop client calls. Those files are official and are served from download.codebuddy.cn over HTTPS, but no page links to them. You reach them by querying the update endpoint directly with a platform parameter for the DEB build, swapping that suffix for the RPM build. The full walkthrough, including the ARM situation and the hash check, is recorded on WorkBuddy Linux install notes.

03 /What did the update endpoint actually return?

A single request returns eight fields, and the values below are copied as observed rather than rounded. The current version is 5.6.2.40046327, the DEB is approximately 410 MB, and the download responds with Server: tencent-cos, which means the file comes from Tencent's own object storage rather than a mirror. The timestamp reads 1790769527, which is 2026-09-30 19:58 local time, and that is the build's release time rather than today. The response also carries supportsFastUpdate: false, so in-app auto-update for WorkBuddy on Linux is not something to rely on.

The command below is the same one the vendor's client uses to check for updates, reproduced without alteration. Run it yourself and compare the hash against the file you receive, because a checksum published by the same site hosting the file proves nothing about where the file came from. Only downloading the WorkBuddy package from the vendor endpoint and comparing byte-for-byte closes that gap. If the values differ, do not install the package.

curl -fsS 'https://www.workbuddy.cn/v2/update?platform=workbuddy-linux-x64-deb' | python3 -m json.tool

04 /What permissions can a Skill ask for?

A Skill is a packaged set of executable scripts and workflows that extends what WorkBuddy can do under your authorisation. Per the official Skills documentation, it is code the assistant can execute rather than a prompt, and it inherits your identity instead of a sandboxed guest account. That inheritance is exactly why the permission list deserves attention before anything is installed. Installed Skills can be disabled without uninstalling, and browsing, uploading, or managing them consumes no credits.

The official security notice lists seven categories a Skill may request. They range from account identity information, contact details, your input content, and usage behaviour logs through third-party platform credentials to local file read and write, and screen and input control. The last two are the ones to think about, because a package holding file access and screen control while running as you is not a toy. Non-official Skills may carry malicious prompt injection, privilege escalation, or backdoors, and some send input to third-party services by design, as WorkBuddy Skills and their permission layers also notes.

Default permission is bounded by the workspace, and "allow full access" is a global switch in the current client that does not carry across devices, per the official Permission Modes documentation, checked on 2026-11-10. Batch-delete approval defaults to 50 items and the automatic backup limit defaults to 3000 MB. Security gateway, end-to-end encryption, and sensitive-data protection are on by default, while the three AI-safety switches are off by default. Those defaults are worth reading before you enable anything that writes files.

The scripts/ directory inside a Skill package runs in the WorkBuddy client sandbox, and the official notice states that Tencent does not take responsibility for the results of those scripts. When a Skill calls a third party, modifies local files, or executes system commands, it does so as you. Complex tasks and complex Skills usually consume more credits, and client-side calls deduct according to task content, but the official Skills Market documentation has not published a specific per-call credits number, checked on 2026-11-10. No number is printed here, because none was published.

05 /How do two community projects cross-check the star count?

Two community GitHub projects grew up around the Linux gap, and both are third-party. Checked on 2026-11-10, the GitHub API reports 63 stars for ziyue67/workbuddy-linux and 56 for jiashuaibei/workbuddy-linux. The first is MIT-licensed Shell and ships a one-click install script plus a four-channel version index; it explicitly excludes Tencent binaries and publishes no provenance files, recording observed values in checksums.json. The second is Python under an "Other" licence and mirrors the official DEB and RPM packages, publishing provenance-deb.json, provenance-rpm.json, SHA256SUMS, and two upstream-response files.

The two counts add up: 63 + 56 = 119, which matches the content pack's original line, 119 stars between them. That agreement is a cross-check of one date's API reading rather than a claim about popularity, and star counts change. The second project also distinguishes reportedSha256 from actualSha256 and states that its own checksum files cannot independently prove official identity. Neither project is affiliated with Tencent, and this site does not treat either as an official source.

06 /How are pages verified before they go live?

Every WorkBuddy page starts from a real search query confirmed through autocomplete rather than guessed from a keyword tool. Most long-tail terms around this product are not yet in the Google Keyword Planner, because the product is too new, so absence of volume data is not treated as absence of demand. Version numbers, download URLs, and HTTP responses are checked against the vendor's own endpoints on the date shown, checked on 2026-11-10. That date only moves when a page is actually re-verified.

Corrections stay visible. If an endpoint moves or a version changes, the fix is noted with a date in the page rather than silently overwritten. Where a page can verify only part of a claim, it says which part; the WorkBuddy Linux page verifies endpoints and package metadata without claiming every distribution will run the package. A page that cannot be verified does not get published, including comparisons that would require running two tools side by side.

07 /What will this site refuse to publish?

The list is short and deliberate. Rewritten press releases are out, because a page that restates the official feature list adds nothing. Fabricated comparisons are out, because I will not claim one tool beats another I have not run against it. Affiliate-driven rankings are out, and nothing on this site is paid placement.

Claims about WorkBuddy's scale I cannot measure are also out: no invented user counts, no benchmarks, no "industry-leading" anything. The same rule applies to numbers that look precise but were never observed. Where a fact is second-hand, it is labelled as such, and where a boundary is unknown, the page says so rather than guessing. That is less impressive than a confident page, but it is the only kind worth keeping.

08 /Where should you start if you are stuck?

If the problem is the install, start with WorkBuddy Linux install notes, which records the endpoint response and the hash check. That page also explains what to do on ARM, where no official arm64 endpoint could be verified. If the problem is broader than one platform, the WorkBuddy download page covers every platform and the builds the official site does not list. It is the shorter read if you only need an installer.

If you want to understand an extension before trusting it, WorkBuddy Skills and their permission layers sets out what a packaged script can reach. The same hub explains how Experts, Skills, and Connectors differ. All of those are collected in the WorkBuddy Answers index, one page per verified question. The index is grouped by platform, by Skills, and by comparison.

If nothing on the shelf fits your workflow, Custom WorkBuddy Skill work sets out the qualifying test and the four things to prepare. Enquiries are quoted per project after samples are seen. If you are weighing this tool against others, a WorkBuddy Comparison limited to local traces states plainly what this machine can and cannot show. Neither page claims that one tool is faster than another.

About WorkBuddy Central records who verifies these pages and the rules they follow. It also carries the independence and trademark statements reproduced on this page. Contact details and the verification rules live there rather than being scattered across the site.

09 /Which open-source Skills are documented here?

Five Skills from this machine were published as public repositories on 2026-11-11. Each now has a page that explains why it was written, how it was developed, what it does and who should use it. None of these pages is a ranking, and none is a recommendation.

• SEO Dev Spec: the numbered site rulebook — why conflicting SEO advice needed identifiers and a conflict table.
• GEO AI Traffic: the seven-step probing Skill — why a baseline of assistant answers has to be logged.
• Presale Validation: the paid-demand framework — why a free waitlist is not a decision rule.
• Game Site Development: the recorded build method — how one over-applied rule produced the A/B/C fact classification.
• Game Site Selection: the embed verification gate — why a blank frame is worse than a small library.

All five repositories are linked from the Skills permission page and from the About page, which is also where the publication date and the verification rules are kept.

10 /Frequently asked questions

Does this guide replace the official WorkBuddy documentation?

No. The official WorkBuddy docs describe the intended path and the feature set in more detail than anything here. These notes cover the gaps around that path: undocumented endpoints, permission boundaries, and corrections with dates. Where the official material is correct, I link to it rather than duplicate it.

Is the Linux package officially supported on every distribution?

No such claim is made here. The vendor's own documentation names only UOS and Kylin as supported Linux targets, and DEB and RPM are packaging formats rather than compatibility guarantees. I verified the endpoint, the response fields, the download URL, the HTTP status, the file size, and the serving infrastructure, checked on 2026-11-10. I have not installed the build on every distribution, and I will not claim otherwise.

Do Skills consume credits, and is there a published per-call number?

Yes to the first part, no to the second. Complex tasks and complex Skills usually consume more credits, and client-side calls deduct according to task content, while browsing, uploading, and managing Skills consume none. The official Skills Market documentation has not published a specific per-call credits number, checked on 2026-11-10. This site prints no number, because inventing one would be worse than leaving it blank.

Is this site affiliated with Tencent?

No. This is an independent site, and it is not affiliated with Tencent, OpenAI, Anthropic, or any product mentioned here. The product belongs to Tencent, and the site says so plainly rather than implying endorsement. The independence statement and the trademark statement are reproduced verbatim at the end of this page.

11 /Why do I recommend WorkBuddy automation for long-running work?

The short answer is composition: custom Skills, MCP connectors, scheduled tasks and a project archive are reachable from one client, and a low-cost model makes repeated jobs affordable. I wrote a full account of WorkBuddy automation: the four-part stack and its per-token cost table, including the cloud sandbox limit on custom models and the price rows I could not verify at source. It is a signed first-hand account, not a paid placement, and it does not publish a winner between agents.

12 /Sources

The public facts on this page come from official documentation, the Automation Guide, Permission Modes, the Skills Market, and the security notice on non-official Skills, read on 2026-11-10. The update-endpoint values and the two community project star counts were checked on 2026-11-10 against the vendor endpoint and the GitHub API. Numbers relayed by media coverage of an enterprise security white paper are not reproduced here, because they are not official documentation. Local observations are limited to what this machine actually recorded, and the date of this page is 2026-11-10.

WorkBuddy Central is an independent site. Not affiliated with Tencent, OpenAI, Anthropic, or any product mentioned.

WorkBuddy is a product of Tencent. Codex is a product of OpenAI. Claude Code is a product of Anthropic. Cursor, Trae, Qoder and CodeBuddy belong to their respective owners. None of them sponsor, endorse, or review this site.

The name "WorkBuddy Central" is descriptive of the site's subject, not a claim to anyone's brand.