Download AlphaWeft, then verify the file before you run it
This is the official download page for AlphaWeft. The button gives you the setup program of about 34 MB, which is the original build, and it does not give the portable .exe. Compare its SHA-256 checksum with the published manifest before you run it.
- Press the download button and wait until the setup program of about 34 MB has been saved to your Downloads folder. The click is recorded on this site, as the privacy page explains. Save it somewhere you can find, because you need its path for the checksum.
- Run the certutil command shown further down this page and compare the SHA-256 value it prints with the value in the published manifest. If the two values differ in even one character, do not run the file.
- Start the setup. If Windows SmartScreen warns, choose More info, then Run anyway, and do so only when the two checksums match. The warning appears because the installer is not code-signed yet.
- Open AlphaWeft, connect a model, press Test to check it and choose the project folder you want to work in. Pick Ask first for the first task, so that every change waits for your approval.
You do not need an account to run AlphaWeft. A cloud AI provider may charge separately for the model you connect, and that charge comes from the provider, not from this site. The built-in model is ready to use without an endpoint of your own. Chats, working folders and API keys stay on your PC, but with a cloud model the prompt and the text of the files the agent reads go to the provider you chose. Work on a local chain or a test network with throwaway accounts, and never paste a private key or seed phrase into a chat.
Requirements and what to prepare
AlphaWeft runs on Windows 10 and 11 on 64-bit (x64) PCs. The interface comes in 13 languages. The file tools work in the chat's working folder, so prepare a folder you may change, and make sure your own build command and test command already run on this PC outside the app, because Shell only runs what you have installed. Shell can run in local Windows, in WSL or over SSH on a server you own; if you want the last option, set up SSH access to that server first. A portable single .exe of about 25 MB also exists, but the button on this page does not give it. Choose a project folder whose files you can afford to change, and put the project under version control first if you can.
Updates after installing
New versions are published automatically, and the app shows an Update button when one is ready. The installer build enables auto-updates. The current version is 2.9.26, released on 2 Nov 2026. Press the button when it appears. If you download a newer installer from this site instead, compare its checksum with the published manifest exactly as you did the first time, because every build has its own value. A new build can change how a tool behaves, so run a small task and read the result after you update.
Verify the file with certutil
certutil -hashfile "C:\Users\you\Downloads\<downloaded file>.exe" SHA256The installer is not code-signed yet, so Windows SmartScreen may show a warning for an unknown publisher. Replace the path in the command with the path of the file you downloaded, run it in a Windows command prompt and compare the long value it prints with the one in the published manifest, character by character. If the values differ, delete the file and download it again from this page. Only a match makes the warning safe to accept. Repeat the check for every installer you download, including later versions.
