Install

Akili Code is a native application. It runs on Linux, macOS and Windows — there is no runtime to install around it.

Linux and macOS

curl -fsSL https://akilios.dev/install.sh | sh

This detects your platform, downloads the matching build, verifies it against the release's SHA256SUMS and refuses to install on a mismatch, then puts both binaries in ~/.local/bin.

Variable	Effect
`AKILI_INSTALL_DIR`	Where the binaries go. Default `~/.local/bin`.
`AKILI_VERSION`	Install a specific version instead of the current one.

Windows

Download the .zip from the download page and unpack it. You get two executables:

akili-code.exe      the CLI and interactive session
akili-code-ui.exe   the desktop application

Put the folder on your PATH so both are available from any terminal. In PowerShell, for the current user:

$dir = "$env:LOCALAPPDATA\Akili"
New-Item -ItemType Directory -Force -Path $dir
# copy the two .exe files into $dir, then:
[Environment]::SetEnvironmentVariable(
  "Path", [Environment]::GetEnvironmentVariable("Path", "User") + ";$dir", "User")

Open a new terminal, then check it:

akili-code --version

Builds are not code-signed yet, so SmartScreen warns on first run: choose More info → Run anyway. That is the honest state of the release, not a marketing gap. Windows Defender may also scan the first launch, which makes it slower than the ones after.

Setting your access token on Windows

PowerShell, for the current user, so it survives a reboot:

[Environment]::SetEnvironmentVariable("AKILI_API_BASE", "https://api.akilios.dev/v1", "User")
[Environment]::SetEnvironmentVariable("AKILI_API_KEY", "akili_live_…", "User")

Or paste nothing at all and put both lines in a .env file beside your project — Akili Code reads it from there too.

What you get

Binary	What it is
`akili-code`	The CLI, and the interactive terminal session
`akili-code-ui`	The desktop application

akili-code --version

Building from source

You need Rust and git.

cargo build --release

On Linux the desktop app needs X11, Wayland and GL development headers first:

sudo apt-get install libx11-dev libxkbcommon-dev libwayland-dev \
  libxcb-render0-dev libxcb-shm0-dev libgl1-mesa-dev libegl1-mesa-dev

File dialogs go through the XDG desktop portal, so GTK development packages are not required.

Platform notes

The engine, Build, Motion and Work's document tools are cross-platform. Four integrations are Windows-only today, and each says so plainly rather than failing quietly: automatic toolchain installs via winget, desktop screen capture, Outlook email, and WSL detection in the environment report. On Linux and macOS the agent routes around them — it will drive headless Chrome to capture a page rather than give up.

FFmpeg is needed only to export a Motion project to MP4. Everything up to and including the scrubbable preview works without it.

NextGetting started → NextBring your own models →