Install guide

Install QwenWork without guessing at prompts

Four screens and one sign-in. The details that actually trip people up are the silent flags, the Gatekeeper prompt on macOS, and the workspace choice on first launch.

Windows: interactive and silent

The exe is a standard NSIS installer. Double-click, accept the default path, and it finishes in under a minute on an SSD. For deployment across many machines, the silent form is:

qwenworkcn-setup-x64.exe /S /D=C:\Program Files\QwenWork

Two notes. /S is case-sensitive, and /D= must be the last argument with no quotes even if the path contains spaces. If you need to install per-user instead of per-machine, omit /D and run the installer as the target user.

macOS: the Gatekeeper prompt is normal

Open the dmg, drag the app to Applications, then launch it. On first run macOS may say the app was downloaded from the internet and cannot be checked. That is Gatekeeper doing its job on a freshly signed binary, not a sign of tampering. Confirm the signature first, then allow it in System Settings → Privacy & Security.

codesign -dv --verbose=2 /Applications/QwenWork.app
spctl -a -vv /Applications/QwenWork.app

Linux: deb, apt, and the sandbox problem

On Debian or Ubuntu, sudo apt install ./qwenworkcn-linux-amd64.deb resolves dependencies in one step. A plain dpkg -i works too but leaves you to fix missing libraries by hand. Running as root is not supported; the client writes to the user profile and refuses to start under a root session.

Fedora, Arch, openSUSE users: the deb will not install and there is no rpm or Flatpak from the vendor. Extracting the deb with dpkg-deb -x sometimes yields a working binary, but updates then have to be done manually. For production use, a Debian container is the more predictable path.

Corporate networks and proxies

The client respects the system proxy on Windows and macOS, and HTTPS_PROXY on Linux. It needs outbound HTTPS to the API and asset domains; a proxy that terminates TLS will break sign-in with a certificate error rather than a clear message. Allow-list the domains instead of intercepting them.

First launch: the workspace question

You will be asked to join a workspace or create one. Choosing personal space gives you a private area with the free quota; joining an organisation brings its own quota, model access and file policies. The two are isolated: files created in personal space do not appear in the organisation, and switching later does not migrate them. Decide before you start generating.

Uninstall and leftovers

Missing a step for your environment? The ticket form asks for exactly the details needed to reproduce an install failure.