Skip to content

Releases: roman-ryzenadvanced/ZCode-v3-Linux-Port

v1.0.0 — ZCode v3.0.0 Linux Port

14 Jun 19:02
@roman-ryzenadvanced roman-ryzenadvanced
v1.0.0
7a4a942

Choose a tag to compare

View all tags
v1.0.0 — ZCode v3.0.0 Linux Port Latest
Latest

What this is

ZCode v3.0.0 running on Linux — unofficially. Z.AI dropped Linux at v3.0.0
(released 2026-06-13), publishing only macOS and Windows builds. The Linux
in-app updater still reports 2.13.0 as the latest version and will never offer 3.0.

This release provides the automation to transform the last official Linux
build (v2.13.0) into a fully working v3.0.0 install.

⚠️ No proprietary binaries are distributed here. ZCode is owned by Z.AI.
This release contains only open-source scripts and documentation. All ZCode
binaries are downloaded at install time from ZCode's own official CDN.

How it works (the short version)

ZCode is an Electron app. v3.0.0 was built with the exact same Electron
(41.0.3 / Chrome 146) and identical native dependencies (node-pty ^1.0.0,
ssh2 ^1.16.0) as v2.13.0. The Node native-addon ABI is therefore identical,
so v2.13's Linux-native prebuilds load cleanly under v3's code.

The port is a surgical file swap:

  • Replace resources/app.asar + resources/glm/ with v3's
  • Add resources/model-providers/ (new in v3)
  • Keep v2.13's app.asar.unpacked/ (Linux node-pty/ssh2), tools/ripgrep/rg,
    and app-update.yml (Linux feed)

Quick start

git clone https://github.com/roman-ryzenadvanced/ZCode-v3-Linux-Port.git
cd ZCode-v3-Linux-Port
chmod +x *.sh
sudo ./install.sh      # downloads official builds + performs the swap
./verify.sh            # confirm v3 is active

Verified working: runtime logs show version=3.0.0, the GLM host answers RPC,
and the ZCode V3 Start Plan (GLM-5.2 + GLM-5-Turbo) entitlements fetch
successfully via app_version=3.0.0. Zero native-module load errors.

Why no .deb in this release?

Re-uploading ZCode's proprietary 278 MB .deb / app.asar / native binaries
would redistribute their commercial software — a copyright/TOS violation and a
legal risk to everyone involved. Standard practice for "unofficial port" repos
is to ship automation that fetches the official files at install time, which
is exactly what install.sh does (it even verifies the SHA-512 of the v3 zip
against Z.AI's published checksum).

Contents

File Purpose
install.sh End-to-end port: download v2.13 deb → install → download v3 mac zip → verify checksum → backup → swap
revert.sh One-command restore to the timestamped backup
verify.sh Check app.asar, Linux native prebuilds, update feed, runtime logs
docs/HOW_IT_WORKS.md Technical deep-dive (Electron ABI, asar anatomy, the aarch64 sshcrypto quirk)
docs/TROUBLESHOOTING.md Common failures and fixes
README.md Full explanation of the Linux gap and the port

Requirements

  • Ubuntu/Debian x86-64 (other dpkg distros work)
  • sudo, curl, unzip, strings, sha512sum
  • ~500 MB free disk

Disclaimer

Not affiliated with, endorsed by, or sponsored by Z.AI. For personal
interoperability use on Linux, a platform the vendor currently doesn't publish
for. If an official Linux build appears, prefer it. MIT license covers this
repo's scripts and docs only — not ZCode itself.

Assets 2
Loading