XIOM -- Download

Latest Release

Fetching release information...

Release notes on GitHub · All releases · machine-readable index

Pre-built Binaries

Platform	Architecture	Archive	Size	SHA256 (expected)
Windows	x86_64	xiom-windows-x64.zip	see release	-
Linux	x86_64	xiom-linux-x64.tar.gz	see release	-
macOS	Intel	xiom-macos-x64.tar.gz	see release	-
macOS	Apple Silicon	xiom-macos-arm64.tar.gz	see release	-
Checksums			SHA256SUMS	-

Downloads are served from the project mirror at dl.xiom-lang.org; the same archives, checksums and attestations are on the GitHub release. The expected SHA256 column is filled from SHA256SUMS next to the release. Archives unpack to bin/ (toolchain executables) and lib/ (standard library and runtime).

Requirements

LLVM/Clang 18 or newer is required. The compiler uses clang to assemble and link every program: winget install LLVM.LLVM (Windows), xcode-select --install (macOS), sudo apt install clang (Debian/Ubuntu), sudo dnf install clang (Fedora).
NASM 2.15 or newer (recommended). It assembles the hardware-accelerated runtime (crypto, memory, context switching) in source builds; released binaries fall back to the C runtime without it. xiom doctor reports whether it was found: winget install NASM.NASM (Windows), brew install nasm (macOS), sudo apt install nasm (Debian/Ubuntu), sudo dnf install nasm (Fedora).
Z3 is optional and not installed separately. The contract verifier (xiom-verify) uses the copy shipped with the toolchain, or a system z3 when present; normal compiles never need it.

Verify your download

The expected SHA256 for each published archive is shown in the table above and listed in SHA256SUMS; every archive also carries a GitHub build-provenance attestation from the release workflow.

# checksum (Windows PowerShell)
Get-FileHash .\xiom-*-windows-x64.zip -Algorithm SHA256

# checksum (Linux / macOS)
sha256sum -c SHA256SUMS

# provenance attestation (GitHub CLI)
gh attestation verify xiom-*-windows-x64.zip --repo xiom-lang/xiom

One-Line Install

The installer downloads the latest archive from the mirror, verifies its SHA256, installs it for your user (no administrator or root needed), and puts the tools on your PATH. It also checks for LLVM/Clang (or the Xcode command line tools on macOS) and tells you how to install them when missing. Pass a release tag to pin a specific version.

# Windows PowerShell
irm https://xiom-lang.org/install.ps1 | iex

# Windows PowerShell (pinned release)
irm https://xiom-lang.org/install.ps1 -OutFile install.ps1
.\install.ps1 -Version <tag>

# Linux and macOS
curl -fsSL https://xiom-lang.org/install.sh | sh

# Linux and macOS (pinned release)
curl -fsSL https://xiom-lang.org/install.sh | sh -s -- --version <tag>

Where it lands: %LOCALAPPDATA%\xiom on Windows, with bin added to your user PATH (use -NoPath to skip; reopen the terminal afterwards), and ~/.local/share/xiom on Linux and macOS, with every tool linked into ~/.local/bin (add XIOM_ADD_PATH=1 to persist the PATH export in ~/.profile). An existing install in that directory is replaced. macOS archives ship once the release workflow enables them; the installer detects the platform and says so clearly when no archive exists yet. Afterwards run xiom doctor to confirm clang, opt and nasm.

Piping a script from the internet runs whatever the server sends. Both installers are short and served from this site - read install.ps1 or install.sh first if you prefer.

Editor Support

Install the toolchain first (above); the editor integration resolves xiom-lsp and xiom-dbg from that install at runtime and never bundles platform binaries. The VS Code extension requires toolchain v0.61.0 or newer.

VS Code -- install XIOM Toolchain (extension 0.12.0) from the Visual Studio Marketplace or Open VSX. It adds diagnostics, hover, completion, references, rename, formatting and DAP debugging. On first run it checks that xiom, xiom-lsp and xiom-dbg are available and tells you when they are missing.
Other editors -- Neovim, JetBrains, Helix, Sublime and Emacs integrate through their LSP/DAP clients; the support matrix is in editors/README.md (Zed planned).
AI agents -- the bundled xiom-mcp server lets MCP-capable agents compile-check code and query the standard library and the package registry; see the compiler guide.

AI-assisted errors (--ai)

--ai asks a model to explain compilation errors and writes the hints to .xiom_ai.json; source files are never modified. Local Ollama needs no key: ollama pull codellama, then xiom --ai --ai-local source.xi. For a cloud key, create .xiom_ai_config.json in your project or in the install directory (%LOCALAPPDATA%\xiom on Windows, ~/.local/share/xiom on Linux/macOS); the project file wins, then the install directory, then your home directory.

{ "provider": "deepseek", "endpoint": "https://api.deepseek.com", "api_key": "sk-your-key-here", "model": "deepseek-chat" }

To change the key later, edit that same file; environment variables like XIOM_AI_KEY override it and command-line flags override both. xiom --help-ai prints every provider and variable. Full walkthrough in Getting Started.

Build from Source

Requires Rust 1.86+ and LLVM/Clang 18+.

git clone https://github.com/xiom-lang/xiom.git
cd xiom
cargo build --release -p xiom
cargo test --workspace --lib

The compiler test suites fetch the matching standard library automatically (scripts/fetch-stdlib.ps1 or .sh).

WASM Playground

No install required. The XIOM compiler compiles to WASM and runs in your browser:

open playground