Latest in AI
Qwen Code 1.0 Preview: Install It Without Confusing the Release Tracks
The Qoder integration is a new preview, but existing Qwen Code installation guides still describe a different release track.
Qwen Code 1.0 Preview is available as native packages for macOS, Linux and Windows, bringing together Qoder and Qwen Code's agent capabilities. To evaluate this specific build, use the tagged preview release rather than assuming an ordinary update command installs it. The preview's configuration and behavior can still change.
The November 11 release is explicitly marked as a prerelease. That distinction matters more than the round version number: a successful installation is not proof that your current plugins, saved sessions and automation behave identically.
Pick the package for your machine
The tagged release includes eight binary archives, alongside GitHub's source archives. Choose by operating system and processor architecture, not by whichever filename appears first.
| Machine | Release archive |
|---|---|
| Apple Silicon Mac | qwen-darwin-arm64.tar.gz |
| Intel Mac | qwen-darwin-x64.tar.gz |
| Linux ARM64 | qwen-linux-arm64.tar.gz |
| Linux x64 | qwen-linux-x64.tar.gz |
| Linux ARM64 using musl | qwen-linux-arm64-musl.tar.gz |
| Linux x64 using musl | qwen-linux-x64-musl.tar.gz |
| Windows ARM64 | qwen-windows-arm64.zip |
| Windows x64 | qwen-windows-x64.zip |
Keep the original archive and record the tag you downloaded. For a controlled evaluation, that gives you a specific artifact to revisit rather than a moving installation script. This guide checks the release assets and documentation; it does not claim to have executed the preview or measured its performance.
Native installation is not new to Qwen Code
The preview does not require a separate Node.js installation. However, it would be misleading to describe that as a capability arriving for the first time with 1.0.
The 0.27.2 README already documents standalone installers. Its alternative npm route requires Node.js 22 or later, and it also lists Homebrew. Those are different installation routes, not evidence that every earlier Qwen Code user needed to manage Node.
The practical change is the preview's integration of the two agent systems and its own release path. If an older npm installation is already on your machine, check which executable your shell resolves before judging the new build:
command -v qwen
qwen --help
On Windows PowerShell, use Get-Command qwen to inspect command resolution. These are inspection steps, not an upgrade recipe. A familiar command name can still point to the older installation, so do not diagnose preview behavior until you know what you are launching.
Connect the provider, then choose the model
The preview-specific README describes a startup connection dialog and /auth for changing the connection during a session. It lists Qwen and Qoder accounts, QwenCloud or Alibaba Cloud Model Studio connections, and other providers or compatible custom endpoints.
After authentication, /model selects an available model. Installing the agent does not grant every model or a universal free quota. Access and charges depend on the provider and account you choose. The preview release is not a pricing announcement for Qwen4-Max, and a working login should not be confused with entitlement to a particular model.
For a first task, use a disposable checkout without production credentials and ask a bounded question such as: “Find the command that runs this project's unit tests and cite the file that defines it. Do not change files.” Check the answer against the repository before allowing a small edit. That gives you a useful baseline without turning setup into a broad autonomous coding session.
Test continuity before moving automation
The preview documents qwen --continue for the most recent session in the same project context, qwen --resume to select an earlier session, and qwen -p for non-interactive requests. It also tells users to configure authentication and permissions before unattended execution.
Try these on a new evaluation session first. Session resumption is a supported feature, but that alone is not a guarantee that every saved session or configuration from an older release migrates unchanged. Review permission prompts, inspect /diff after edits and check the actual test output rather than accepting a completion message as proof.
Teams depending on older Web Shell, SDK or channel workflows should keep those workflows on their known working build until they validate the preview equivalents. This is a migration recommendation, not a claim that those features have been removed. The preview documentation explicitly allows interface and behavior changes, so absence from its short overview should not be converted into either a compatibility promise or a removal notice.
A version number is a poor deployment criterion for an agent that can modify a repository. The useful milestone is reproducing your own task, permissions and recovery path on the exact build you plan to use.
I’m Paras. I work at the intersection of AI, engineering and distribution.
I help technical teams turn product changes and migration details into useful developer-facing content.