Portable & offline

Portable QwenWork the honest version

There is no green build, no single exe, no unzip-and-run package. Anyone offering one is shipping a repack. These are the three approaches that work within what the vendor actually publishes.

No official portable build exists. The desktop client is an installer-based application that writes to the system application directory and registers a protocol handler. A file claiming to be a portable or green version of QwenWork is a repack with unknown modifications, and it cannot pass a signature check against the vendor.

Option 1: offline installer for machines without internet

Download the package on a connected machine, copy it over, then install. Two things must be carried along or the install will fail at first launch: the WebView2 Evergreen runtime on Windows, and the app package itself. Keep them in the same folder with a short readme stating the version and hash — six months later that note is the only thing that makes the folder usable.

PlatformPackageSide load
Windows x64setup-x64.exeWebView2 Evergreen Standalone Installer
Windows ARM64setup-arm64.exeWebView2 Evergreen Standalone Installer (ARM64)
macOSdarwin-arm64.dmgNothing extra; Rosetta only if running the Intel build
Linuxlinux-amd64.debDependencies resolved by apt at install time

Option 2: per-user install on an external drive

On Windows, running the installer as the signed-in user without /D places the app under the user profile, which can live on a removable drive. It is not truly portable: registry entries, the protocol handler and the WebView2 runtime stay on the host, so the drive only works on machines that already have those. In practice this is useful for moving between two machines you control, not for walking into a client site.

Option 3: export configuration, not the application

What people usually want from a portable build is the settings and the workspace layout travelling with them. That part is supported: the app's configuration directory is plain JSON, and copying it to a second installation reproduces the layout. Sign-in state does not travel, by design — it is bound to the device, which is also why a stolen config folder is not a stolen account.

%APPDATA%\QwenWork            → Windows
~/Library/Application Support/QwenWork  → macOS
~/.config/QwenWork                → Linux

Corporate images and golden masters

Setting up an internal distribution point? The channel page sets out which sources are official and which are repacks.