Install Arashi

Choose the install method for your platform and environment.

Use aw for the workflows in this guide. The arashi executable remains supported for existing scripts and workflows.

Prerequisites

git available in your shell
bash and curl for the macOS/Linux installer path
Windows PowerShell for the Windows installer path
node and npm for the npm path

Method 1: macOS/Linux installer

curl -fsSL https://arashi.haphazard.dev/install | bash

Pin a specific version when needed:

curl -fsSL https://arashi.haphazard.dev/install | ARASHI_VERSION=1.16.0 bash

Verify install:

aw --version

The installer defaults to ~/.arashi/bin, updates your shell profile so the installed executables are available on PATH in new shells, and in interactive installs can offer shell integration for aw switch --cd. It also runs a quick aw --version smoke test before declaring success. The macOS/Linux installer provides both arashi and aw and routes them to the same Arashi release.

For unattended installs, set ARASHI_SHELL_INTEGRATION=yes to enable that automatically or ARASHI_SHELL_INTEGRATION=no to skip it.

Method 2: Windows PowerShell installer

powershell -c "irm https://arashi.haphazard.dev/install.ps1 | iex"

Inspect the script before running it:

irm https://arashi.haphazard.dev/install.ps1

Pin a specific version when invoking a downloaded script:

.\install.ps1 -Version 1.16.0

The PowerShell script is the canonical Windows installer. The PowerShell installer provides both arashi and aw for Git Bash, PowerShell, and Command Prompt. By default, it installs arashi.bin.exe, the extensionless arashi command for Git Bash, arashi.ps1, arashi.bat, the extensionless aw command for Git Bash, aw.ps1, and aw.bat in %USERPROFILE%\.arashi\bin, adds that directory to the persistent user PATH, and tells you to open a new terminal. Both names execute the same native binary. Open a new Git Bash window before running aw --version so it inherits the PATH change. Use -InstallDir or ARASHI_INSTALL_DIR for a custom user-writable directory. Use -NoModifyPath or ARASHI_NO_MODIFY_PATH=1 to leave PATH unchanged and add the install directory to PATH yourself. The installer does not edit Git Bash profile files.

Method 3: npm global install

npm install -g arashi

Arashi downloads the matching platform binary on first use. To preinstall it explicitly:

aw install

npm installs provide both arashi and aw; both names use the same package and platform binary.

For npm-managed bootstrap automation, aw install -j and aw install --json are equivalent and emit the same machine-readable result exactly once.

Verify install:

aw --version

Inspect the workspace after installation:

aw status

Manual macOS/Linux fallback

Download arashi-macos-arm64 (Apple Silicon) or arashi-linux-x64 (Linux x64), plus arashi, aw, and arashi-checksums.txt from the same GitHub release. Compare each payload’s SHA-256 hash with the manifest using shasum -a 256 on macOS or sha256sum on Linux; stop if any differs.

Rename the native binary to arashi.bin, place it beside arashi and aw in a user-writable directory on PATH, and run chmod +x arashi.bin arashi aw there. Open a new shell, run aw --version, and confirm both installed executable entrypoints report the same version. Manual installs must be removed manually; aw uninstall does not remove them.

Manual Windows fallback

If you do not want to pipe a remote script into PowerShell, download these assets from the same GitHub release:

arashi-windows-x64.exe
arashi
arashi.ps1
arashi.bat
aw
aw.ps1
aw.bat
arashi-checksums.txt

Download and verify the complete set from one GitHub release. Verify all seven payload assets against arashi-checksums.txt with Get-FileHash -Algorithm SHA256, rename the source binary arashi-windows-x64.exe to arashi.bin.exe, and put arashi.bin.exe, arashi, arashi.ps1, arashi.bat, aw, aw.ps1, and aw.bat together in one directory on PATH. Open a new shell and confirm that both installed executable entrypoints report the same version. Manually placed wrappers have no direct-installer ownership ledger. Before migrating to the official installer, deliberately move or remove the complete manual payload if any file reports a collision.

Troubleshooting and fallback

command not found: install missing prerequisite (curl, bash, npm, node, or PowerShell) and rerun.
Permission errors writing to global paths: rerun the direct installer with a user-writable install directory or use a user-level npm prefix.
Network/download failures: retry once; for npm installs you can rerun aw install, then switch to another install method if needed.
Checksum mismatch on direct installer paths: stop and use npm/manual fallback, then report the failure.
If aw --version exits immediately or returns code 137, rerun the direct installer with ARASHI_VERSION=<version> or -Version <version> to pin a known-good release, or use npm/manual install while reporting the bad release artifact.
PATH changes may require a new terminal on Windows and POSIX shells.
If Git Bash reports arashi: command not found after a PowerShell install, confirm %USERPROFILE%\.arashi\bin is on the persistent user PATH, then open a new Git Bash window. An already-open shell does not inherit the update.
With -NoModifyPath, add the install directory to PATH yourself. Do not add an installer-managed entry to .bashrc, .bash_profile, or .profile; the installer does not edit Git Bash profile files.
If your environment blocks local .ps1 scripts, inspect install.ps1 first, then add -ExecutionPolicy Bypass to the powershell invocation for this one process or use the manual Windows fallback.
If installation reports an unrelated existing aw command on PATH or at the destination, inspect it and deliberately move or remove it before retrying. Arashi does not overwrite or shadow unrelated commands.
A user-created shell alias for aw is an unsupported interim workaround for older releases, not equivalent to the supported executable. Upgrade to a release that provides both names, then remove the workaround so shell integration and completion can manage aw safely.