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 Windows installer

One file, akili-code-<version>-windows-x64-setup.exe. Run it and you get a proper installation:

Akili Code in the Start menu — search for it, open it, pin it to Start or the taskbar.
Akili Code CLI in the Start menu too, which opens the interactive session in a terminal.
akili-code on your PATH, so typing it in any new terminal starts the interactive session — the same as on Linux.
An entry in Settings → Apps, with a clean uninstaller.
An optional desktop shortcut, offered on the last page.

It installs for your account only, into %LOCALAPPDATA%\Programs\Akili Code, and never asks for an administrator. That is deliberate: it is also what lets akili-code update replace its own files later without a UAC prompt. Nothing else is needed — the Visual C++ runtime is built in, so a freshly set-up PC runs it as-is.

Open a new terminal afterwards and check it:

akili-code --version
akili-code            # the interactive session, in whatever folder you are in

Why a new terminal? Windows hands the updated PATH only to programs started after it changed. A PowerShell window that was already open will say akili-code is not recognised until you open another one.

The installer is not code-signed yet, so SmartScreen warns the first time: 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.

Installing without clicking

For scripts and fleets, the installer takes the standard silent switch, and the install folder can be changed:

akili-code-0.1.14-windows-x64-setup.exe /S
akili-code-0.1.14-windows-x64-setup.exe /S /D=C:\Tools\Akili Code

/D= must come last and is not quoted, even with spaces — that is how every NSIS installer reads it.

Uninstalling

Settings → Apps → Akili Code → Uninstall. It removes the programs, the shortcuts and its PATH entry, and nothing else: your settings, sign-in and project sessions are kept, so reinstalling picks up where you left off. The PATH entry is removed on its own, without touching the rest of your PATH.

Prefer a zip?

The .zip is still published beside the installer on the download page, for anyone who would rather manage the files themselves. It contains the same two programs; you put them on PATH yourself.

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, and so now are the two integrations that were not: automatic toolchain installs use Homebrew on macOS and apt, dnf, pacman, apk or zypper on Linux, and screen capture uses screencapture on macOS and whichever of grim, gnome-screenshot, spectacle, maim, scrot or import the machine has. Where a tool is genuinely missing, each names what to install rather than refusing.

One integration remains Windows-only, and says so plainly: Outlook email, which goes through your local Outlook profile. Gmail and Google Drive work on every platform through connectors. WSL detection in the environment report is Windows-only too, for the obvious reason.

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

Keeping it current

akili-code update installs the current release, verifying it against the release checksums first. See Updating.

NextUpdating → NextBring your own models →