Windows
Professional setup wizard for Windows 10/11 desktop users.
- 64-bit installer
- Desktop shortcuts
- Launch-after-install flow
- Signed build verification
Prepare AiCodeStation on Windows for voice-driven tool launch, controlled command workflows, project scanning, GitHub operations, dependency visibility, and cleaner movement from local development to protected production usage.
Get the right desktop build for Windows or Linux. macOS is coming soon.
Professional setup wizard for Windows 10/11 desktop users.
macOS build for Apple Silicon and Intel, coming soon.
Flexible Linux builds for developer workstations and server-side workflows.
The newest Windows build. Every file inside it is signed. Unzip it and run AiCodeStation.exe — nothing is installed, and the app updates itself from Settings → Updates. The setup wizard above is still 1.0.30.
One executable that runs on any modern Linux distribution. No install, no root, no package manager — it carries the libraries it needs.
Download AppImageInstalls with dnf or zypper, which resolve the system libraries first. One package for all three families.
Download .rpmFor machines that already have the Qt system libraries. On a clean system it will not start — use the AppImage or the .deb, which bring those libraries with them.
Download .tar.gzCommand-line utilities for repeatable tool execution, scripting, local automation, and developer workflow control.
View CLI toolsVersion history, changes, fixes, upgrade notes, compatibility updates, and release visibility for every build.
Read release notesVerify installer integrity before running downloads in production, enterprise, or security-sensitive environments.
Verify buildVerify your download before running it. Compare the SHA-256 checksum of the file you downloaded against the official value for release 1.0.30 shown below.
WindowsAiCodeStation-Setup-1.0.30.exe
e795b70ae550d585c6b95eacb4a6bfdb0c87bf7c571dbe076eb20655f0c42e70
Windows portableAiCodeStation-1.0.33-windows-x86_64.zip
29b4d9164cbe876acd6c53c0390697bfcd290e58bb08e5ffe1406fe1235c6abf
Linux .debaicodestation_1.0.30_amd64.deb
a05f7ee5dcd06455c2c141d15bd08b92eaac68655fa6fc8e8433d15074f33371
Linux .rpmaicodestation-1.0.30-1.x86_64.rpm
bf633f769b67331f952f5b84a6285a6335c34d5eb0c77d34408363dddf35d3bf
AppImageAiCodeStation-1.0.30-x86_64.AppImage
4430203b37e8120ec0cdb3d92e5da5f4bff1c8ce156a6d7bc7adbd250e0f8fbd
Linux tar.gzAiCodeStation-1.0.30-linux-x86_64.tar.gz
bb48690618b6e54a18e0c61829c51ce757c8ce0fc569ccd114c943194f4bd9ba
A checksum printed on this page proves the file did not arrive corrupted. It cannot prove the page itself was not changed. Every release file is therefore also signed, and the signing key is on neither the server that hosts this page nor the one that hosts the downloads.
Release key fingerprint
E779 76A5 D8A6 1752 8244 D939 E4E6 5E94 12CD 53CA
Verify a download
gpg --import aicodestation-release-key.ascgpg --fingerprintgpg --verify aicodestation_1.0.30_amd64.deb.asc aicodestation_1.0.30_amd64.deb
Compare the fingerprint gpg prints against the one above before trusting anything else. gpg will also warn that the key is not certified by a trusted signature — that is expected and is not a failure. It means only that you have not personally vouched for the key. A signature sits beside every download, along with a signed SHA256SUMS.txt.asc.
Add the repository once and AiCodeStation updates with the rest of your system. The signature is checked by the package manager on every update, not only the first time — which is the part a downloaded file cannot give you.
Debian, Ubuntu, Mint
curl -fsSL https://acsdownloads.blob.core.windows.net/releases/aicodestation-release-key.asc | sudo gpg --dearmor -o /usr/share/keyrings/aicodestation.gpgecho "deb [arch=amd64 signed-by=/usr/share/keyrings/aicodestation.gpg] https://acsdownloads.blob.core.windows.net/releases stable main" | sudo tee /etc/apt/sources.list.d/aicodestation.listsudo apt update && sudo apt install aicodestation
Fedora, RHEL, openSUSE
sudo tee /etc/yum.repos.d/aicodestation.repo <<'EOF'[aicodestation]name=AiCodeStationbaseurl=https://acsdownloads.blob.core.windows.net/releases/enabled=1repo_gpgcheck=1gpgcheck=0gpgkey=https://acsdownloads.blob.core.windows.net/releases/aicodestation-release-key.ascEOFsudo dnf install aicodestation
Why gpgcheck=0 is correct here. That setting governs a signature embedded
inside the .rpm file, which this package does not carry. The package is still covered, by a
chain dnf verifies on every transaction: the repository index is signed, the index names the
checksum of the package list, and the package list names the checksum of the package. That is
what repo_gpgcheck=1 switches on, and it is on. A tampered package
fails it.
bb48690618b6e54a18e0c61829c51ce757c8ce0fc569ccd114c943194f4bd9ba *AiCodeStation-1.0.30-linux-x86_64.tar.gz e795b70ae550d585c6b95eacb4a6bfdb0c87bf7c571dbe076eb20655f0c42e70 *AiCodeStation-Setup-1.0.30.exe a05f7ee5dcd06455c2c141d15bd08b92eaac68655fa6fc8e8433d15074f33371 *aicodestation_1.0.30_amd64.deb bf633f769b67331f952f5b84a6285a6335c34d5eb0c77d34408363dddf35d3bf *aicodestation-1.0.30-1.x86_64.rpm 4430203b37e8120ec0cdb3d92e5da5f4bff1c8ce156a6d7bc7adbd250e0f8fbd *AiCodeStation-1.0.30-x86_64.AppImage
Official SHA-256 checksums for AiCodeStation 1.0.30. Compare them with the file you downloaded.
Get-FileHash .\AiCodeStation-Setup-1.0.30.exe -Algorithm SHA256sha256sum aicodestation_1.0.30_amd64.debThe Windows path is designed for builders who want less manual command typing and more structured execution: launch tools, inspect projects, manage workflows, and keep important actions tied to an account-backed product experience.
Use the desktop command station to reduce repeated tool opening, command switching, and manual setup friction across local development tasks.
Keep command workflows, scans, and tool usage inside a more controlled workspace instead of spreading operations across disconnected windows.
Support project checks, dependency visibility, repository context, and workflow review so builders can move faster with fewer blind spots.
Create a free account, install the desktop app, launch your tools, then scale into team controls when ready.
Create a free account first so downloads and product usage stay account-backed. No checkout, card, or subscription is required for the Free plan.
Download the build for your operating system and install the desktop command station.
Run voice, command, GitHub, scan, and workflow actions with less repeated manual work.
Move into team policies, governed access, and company workspace controls when the workflow grows.
Faster tool launch, cleaner project checks, and controlled execution from your desktop.