Install and download
Download Ku 0.0.18 revision 1 (v0.0.18-r1) for your operating system and CPU. The CLI and extension still report 0.0.18.
Choose your platform
Section titled “Choose your platform”Download the target archive below, its manifest and SHA256SUMS from the v0.0.18-r1 Release. native_ci-* artifacts are CI examples, not CLI installers.
| System | Architecture | Archive |
|---|---|---|
| macOS | Apple Silicon / arm64 | ku-v0.0.18-aarch64-apple-darwin.tar.gz |
| Windows | x64 / MSVC | ku-v0.0.18-x86_64-pc-windows-msvc.tar.gz |
| Linux | x64 / GNU | ku-v0.0.18-x86_64-unknown-linux-gnu.tar.gz |
Download checksums: SHA256SUMS
No other platform archives have been verified. Cross compilation support does not mean every operating system or architecture has a published package.
Extract and verify
Section titled “Extract and verify”- Verify the archive against the Release
SHA256SUMS. A separate.manifest.jsondescribes archive and file integrity. Checksums are integrity checks, not publisher signatures. - Extract the entire archive into an empty directory and read
README-INSTALL.md. Preserve the relative layout ofku,libku.rlib,deps/, andnative-tls/. - Check the version from that directory. On macOS / Linux:
./ku --versionOn Windows PowerShell:
.\ku.exe --versionThe reported version should be 0.0.18. Optionally add this directory to PATH, then run ku --version. Install the bundled ku-language-0.0.18.vsix for VS Code integration.
Interpreter and VS Code extension
Section titled “Interpreter and VS Code extension”Each platform archive above includes the Ku CLI (ku run uses the interpreter) and ku-language-0.0.18.vsix. The extension is distributed inside those archives, without a separate VSIX download asset. This website does not provide an in-browser interpreter.
After extraction, choose … → Install from VSIX… in the VS Code Extensions view, open ku-language-0.0.18.vsix, and reload the window. Alternatively, run this from the extracted directory:
code --install-extension ./ku-language-0.0.18.vsix --forceThe extension also needs the Ku CLI. Add the extracted directory to PATH, or set ku.executablePath in VS Code to the full path of ku (ku.exe on Windows).
Runtime and build requirements
Section titled “Runtime and build requirements”| Operation | Additional requirements |
|---|---|
ku run hello.ku / ku check hello.ku |
Ku CLI for the matching platform |
Default ku build hello.ku |
Rust 1.89.0 for the target and its system linker; retain the bundled Rust dependencies |
ku build --backend c hello.ku |
A working target C compiler and linker |
| Native database program | Matching external database client dynamic libraries; they are not bundled |
The default runner embeds only the entry source. Imported modules still load from their original locations. Source independent deployment of a complete local import graph requires native C compilation and remains subject to the backend support limits.
Try the development source
Section titled “Try the development source”From a local checkout of the repository:
cargo +1.89.0 run --locked --release -- --versioncargo +1.89.0 run --locked --release -- run examples/hello.kuThe CLI and Cargo version for this release is 0.0.18. Record the Git commit, target and toolchain when building source; source-build success does not prove publication of a release artifact.
Uninstall
Section titled “Uninstall”For an archive installation, remove the directory you extracted, undo any PATH entry you added, and uninstall the VS Code extension. Preserve any source files and configuration you created there first. No separate one click installer, package manager installation, or ku uninstall command has been verified.
Next: run your first program. Source for the installation contract: release archives.
ku supervise has platform-specific prerequisites and memory metrics; see support boundaries. The macOS CLI can run programs, but this isolation mode is not natively supported.