The Connector supports Windows 10 and Windows 11 on both amd64 and arm64.
Open PowerShell and run:
$
irm https://connector.kuali.co/install.ps1 | iex
The script picks the right build for your CPU (amd64 or arm64), downloads it to %LOCALAPPDATA%\Programs\kuali\kuali.exe, and adds that folder to your user PATH. No admin rights required.
Open a new PowerShell window when it finishes so the updated PATH takes effect.
Set KUALI_VERSION to any published release tag — with or without the v prefix:
$
$env:KUALI_VERSION = '1.0.0-rc14'
$
irm https://connector.kuali.co/install.ps1 | iex
Without KUALI_VERSION, the script installs the latest stable release.
Open the latest release.
Download kuali-windows-amd64.exe (most PCs) or kuali-windows-arm64.exe (Copilot+ PCs and other ARM machines).
Rename the file to kuali.exe.
Move it to a folder on your PATH. A common choice is %LOCALAPPDATA%\Programs\kuali\:
$
$dir = "$env:LOCALAPPDATA\Programs\kuali"
$
New-Item -ItemType Directory -Force -Path $dir | Out-Null
$
Move-Item -Force "$HOME\Downloads\kuali-windows-amd64.exe" "$dir\kuali.exe"
Add that folder to your user PATH if it isn't there already:
$
[Environment]::SetEnvironmentVariable(
"PATH",
"$env:PATH;$env:LOCALAPPDATA\Programs\kuali",
"User"
)
Open a new PowerShell window so the updated PATH takes effect.
If you use Windows Subsystem for Linux, install the Linux build inside your WSL distro — see the Linux guide. An AI client running on Windows can still call a Connector installed in WSL if you point the MCP config at the WSL binary path (\\wsl$\Ubuntu\home\you\.local\bin\kuali).
Windows SmartScreen may warn the first time you run an unsigned executable.
Click More info, then Run anyway. You'll only see this once per machine.
$
kuali version
If the command isn't found, PATH likely didn't pick up the new folder — close and reopen PowerShell, or sign out and back in.
$
Remove-Item "$env:LOCALAPPDATA\Programs\kuali" -Recurse -Force
$
Remove-Item "$HOME\.kuali" -Recurse -Force
To remove the directory from your PATH, open Settings → System → About → Advanced system settings → Environment Variables, find Path under User variables, edit, and remove the …\Programs\kuali entry.
If you stored API keys in Windows Credential Manager (via kuali setup or kuali auth login), open Credential Manager → Windows Credentials and delete the entries under the kuali-cli service.
Last updated: September 21, 2026
ON THIS PAGE
Once kuali version works, head to Getting started to connect your instance and AI assistant.
Getting started ->
Ready-to-use prompts for curriculum, research, build apps, imports, workflow analysis, and reporting.
Browse prompts →
Tips for Claude Desktop, Claude Code, Codex, Gemini, Copilot, and VS Code.
AI assistants →
Skip the chat — every capability is also a plain kuali command, ready for scripts and CI.
Command reference →