Install
Requirements: Linux, macOS, or Windows 10/11. The installer bundle ships its own Node.js runtime; installing from npm instead needs Node.js 22.12 or newer on PATH.
Installer script (recommended)
Section titled “Installer script (recommended)”Linux and macOS:
curl -fsSL https://kurahi.com/install.sh | bashWindows (PowerShell 7 or Windows PowerShell 5.1):
iwr -useb https://kurahi.com/install.ps1 | iexThe installer:
- picks the release bundle for your OS and CPU from GitHub Releases (
kolo-<version>-<os>-<arch>.tar.gz,.zipon Windows); - verifies its SHA-256 against the
SHA256SUMS.txtpublished with the release before unpacking; - installs under
~/.local/share/kolo/<version>(Windows:%LOCALAPPDATA%\KoLo\app\<version>) and links thekolocommand into~/.local/bin(Windows:%LOCALAPPDATA%\KoLo\bin, added to your user PATH); - runs
kurahi init --non-interactiveandkurahi service install; - prints a one-use pairing invitation for a second device or terminal.
Nothing is downloaded from anywhere but github.com, and nothing runs as root or administrator.
Flags (install.sh --help, install.ps1 -?):
| Flag | Effect |
|---|---|
--version <v> / -Version |
install a specific release |
--prefix <dir> / -Prefix |
install directory |
--bin-dir <dir> / -BinDir |
where the kolo command is linked |
--name <id> / -Name |
identity name for the first run (default default) |
--no-init, --no-service, --no-invite / -NoInit, -NoService, -NoInvite |
skip a step |
--bundle <file> --sums <file> / -Bundle -Sums |
install from a local bundle (offline, air-gapped) |
--dry-run / -DryRun |
print the resolved asset and paths; download nothing |
Both scripts are in the repository under scripts/ and are served unchanged. Read them before piping them into a shell if your policy requires it.
Offline or air-gapped
Section titled “Offline or air-gapped”Download the bundle and SHA256SUMS.txt from the releases page on a connected machine, copy both files over, then:
bash install.sh --bundle kolo-<version>-linux-x64.tar.gz --sums SHA256SUMSFrom source
Section titled “From source”git clone https://github.com/koda-tokyo/kurahi.gitcd kurahipnpm install --frozen-lockfilepnpm buildnode kolo.mjs --versionpnpm build && node scripts/bundle.mjs produces the same bundle the installer uses, for your OS and CPU, under release/.
After installing
Section titled “After installing”kurahi init # if you skipped it: state directory, config, gateway token, doctorkurahi service install # gateway under systemd / launchd / Task Schedulerkurahi health # one status linekurahi tui # talk to the agentSee Getting started, Gateway service and Pairing.
Updating and removing
Section titled “Updating and removing”kurahi updatechecks for and installs a newer release;kurahi update statusshows the current channel and version. See Updating.kurahi uninstall --allremoves the service, the state directory and the workspace; delete the install directory and thekololink to remove the program. See Uninstall.
Troubleshooting
Section titled “Troubleshooting”kolo: command not foundafter install: open a new terminal, or add the bin directory printed by the installer to PATH.Node.js ... is required: install Node 22.12 or newer from https://nodejs.org and re-run the installer.SHA-256 mismatch: the download is corrupt or altered. Do not install it; re-run the installer, and report persistent mismatches to security@kodasoken.com.- Windows SmartScreen or an endpoint agent blocks the script: save it, review it, and run it with
pwsh -ExecutionPolicy Bypass -File install.ps1.