Pick how you want to run it. We'll walk you through it one step at a time. The terminal and desktop downloads aren't code-signed yet, so macOS and Windows may warn you the first time; the steps below show you what to click.
Terminal on macOS · 8 steps
Terminal on Linux · 7 steps
Terminal on Windows · 8 steps
Desktop app on macOS · 6 steps
Desktop app on Windows · 6 steps
Desktop app on Linux · 5 steps
In your browser · 3 steps
Apple and Microsoft want developers to buy a signing certificate, so the system can tell who published an app. We haven't yet, so macOS and Windows treat our downloads as coming from an unknown publisher. The warning is about identity, not a detected problem. Only bypass it for files from myaielia.com or github.com/3IVIS/buildaharness/releases. Linux shows no warning. We plan to sign the builds later.
Terminal releases come with a .sha256 file, and the same hashes are in aielia-latest.json. The installers check this for you. To check a manual download:
shasum -a 256 aielia-darwin-arm64 # macOS sha256sum aielia-linux-x64 # Linux Get-FileHash .\aielia-win32-x64.exe # Windows (PowerShell)
The result must match the .sha256 file. Desktop installers don't have published checksums yet.
Get it from the newest aielia-v… release on GitHub Releases. Then, on macOS and Linux, make it runnable; on macOS also clear the download mark; on Windows, unblock it:
chmod +x aielia-darwin-arm64 xattr -d com.apple.quarantine aielia-darwin-arm64 # macOS only ./aielia-darwin-arm64 --version Unblock-File .\aielia-win32-x64.exe # Windows
Uninstalling never deletes your chats. Delete these folders yourself if you want them gone.
Terminal: ~/.buildaharness/personal-assistant/. Uninstall by deleting the aielia program (Windows: the %LOCALAPPDATA%\Aielia folder and its PATH entry).
Desktop: macOS ~/Library/Application Support/com.buildaharness.assistant/; Linux ~/.local/share/com.buildaharness.assistant/; Windows %LOCALAPPDATA%\com.buildaharness.assistant\. The desktop app doesn't update itself yet: install a newer release over the old one.
Yes, and a build you compile yourself carries no warning. You need Node.js (we use 22) and, for the desktop app, Rust 1.88 or newer.
git clone https://github.com/3IVIS/buildaharness cd buildaharness npm ci npm run build:harness && npm run build:runtime && npm run build:aielia npm run dev:desktop
Something else (often an npm-linked aielia) is already there. Remove it, or re-run with force: curl -fsSL https://myaielia.com/install.sh | sh -s -- --force, or on Windows set $env:AIELIA_FORCE = '1' first.
Still stuck? Open an issue on GitHub with your system, which download you used and the exact message.
Begin with a simple question, then ask for something serious like sending an email, and watch Aielia stop and ask first. This is an early alpha; read how it works before turning on file or command access.