Skip to content

Download

Latest version: 26.10.0 (released 2026-10-06)

简体中文：下载页

Main channel: GitHub Releases

Download the Windows installer (direct link)

That link is the file itself: job-workbench-setup-26.10.0-win64.exe — a Windows x64 installer with wizard-style setup; no Python or Node needed. If the direct link does not open (freshly published, CDN not synced yet), open the release page and pick the file from the Assets section.

GitHub can be slow or unreachable from some networks. If the release page will not open, or a download keeps breaking, use the backup channel below.

Backup channel

Leave a message in the Gitee mirror's Issues telling us which version you need — Gitee is reachable from mainland networks without opening GitHub first; we will reply with a working backup download link. (The main repository's Issues work too when GitHub is reachable.)

To be precise: the installer is 130+ MB, above Gitee's 100 MB attachment limit, so the backup channel can only hand out links (cloud storage etc.), never host the file on Gitee itself; backup links are maintained manually and may lag behind the official release. Please use the main channel whenever GitHub is reachable for you.

Unsigned installer and SmartScreen

The installer is not code-signed yet. On first run, Windows may show "Windows protected your PC" — the standard prompt for unsigned software: click More info → Run anyway.

SmartScreen reputation rebuilds per version, so later releases may prompt again; the missing signature does not affect auto-update (integrity is checked against the hash in latest.yml).

Verify the download

Starting with v26.9.0, each release ships SHA256SUMS.txt (SHA256 hashes of the installer and latest.yml). After downloading, run this in PowerShell or CMD (substituting the file you actually downloaded):

certutil -hashfile job-workbench-setup-26.10.0-win64.exe SHA256

Compare the output with the hash for the same file in SHA256SUMS.txt on the release page: a match means the file is intact and identical to what the publisher uploaded. To be precise, this proves integrity; for an unsigned build it is not proof of publisher identity.