GitHub
QwenWorkNo repository, and why that matters
Searching GitHub for the client turns up forks of unrelated projects and repackaged installers. Here is the factual situation, stated plainly.
The facts
- The desktop client is a closed-source commercial application. There is no public source tree.
- No official issue tracker on GitHub, so a GitHub issue is not a support channel.
- No SDK or CLI published to npm, PyPI or any other public registry.
- The vendor's official site and in-client help are the only supported channels.
What you will find if you search anyway
Two categories, both of which should be treated with suspicion: forks of unrelated open-source projects that happen to share a name, and repositories offering 「QwenWork installers」 — those are repacks, and a repack cannot carry the vendor signature. A repository with the right name and the wrong signer is the classic distribution route for a modified installer.
How to report a bug without an issue tracker
- Reproduce it twice
Once is an anecdote; twice is a report.
- Write the five fields
System, version, exact error, what you tried, timestamp. The ticket page has the template.
- Send it through the client's help menu
That is the supported path, and it attaches diagnostics automatically.
- Post the reproduction, not the complaint, in the forum
Others may have hit the same wall and can confirm the pattern.
Open-source alternatives, if that is the requirement
If a public repository is a hard requirement — for audit, for air-gapped builds, for modification — then a closed-source commercial client will not satisfy it, and no amount of searching changes that. The honest options are to use the web client (nothing to audit, nothing to install) or to pick a different tool whose licence actually permits what you need.