Release notes
QwenWork2.1.0 release notes
Written for the person who has to roll it out, not for the person who has to announce it. Four areas changed; three of them need a re-check on existing machines.
Release 2.1.0, built 2026-11-18
Two weeks after 2.0.2, this is a consolidation release rather than a new surface. The 2.0.0 feature set — collaboration space, automation — is unchanged in shape; what moved is the plumbing around it.
Packages
All six installers were rebuilt. Sizes shifted by a few megabytes, which matters more than it sounds: the numbers people saved in deployment notes are now wrong. The Windows ARM64 package is noticeably smaller than in 2.0.2 because unused runtime components were removed.
Workspace switching
Switching between personal space and an organisation no longer forces a sign-out cycle. The side effect is worth knowing: the active workspace is remembered per device, so a shared machine may open in the previous user's workspace. If you run a lab or a shared edit station, add 「sign out when done」 to the routine.
Automation
Event triggers now cover ten types, and the rate limit is stated plainly: 200 runs per hour per workspace, ten active tasks on the free tier. Failures report the step that broke instead of a generic error — the single most useful change in this build for anyone running scheduled jobs.
Signing
Hashes changed for every package, as they do with every release. The macOS builds remain notarised; spctl should still answer source=Notarized Developer ID. Linux packages still ship without a detached GPG signature, so hash comparison against the published value remains the practical check.
Three things to re-check on existing machines
- Re-verify hashes before rolling out
If you keep a pinned package for images, its recorded hash no longer matches what the path serves. Confirm which one you are deploying.
- Re-test one automation end to end
The trigger surface changed. A task that fires on a file event should be watched once rather than assumed.
- Check shared workstations
Per-device workspace memory means the previous user's workspace can greet the next person.
Rolling back if 2.1.0 misbehaves
Keep the 2.0.2 package until a week of real work has passed. Downgrading is an uninstall followed by the older installer: local project files survive, cloud task history does not follow you back.
- Uninstalling keeps %APPDATA%\QwenWork unless the box is ticked — that folder holds cached credentials and the local index.
- Shared agents created in 2.1.0 stay in the workspace after a downgrade; they simply do not appear in the older client.
- Automation schedules keep firing on the server. Disable them before you roll back, or they will run against a build that no longer understands them.