Installation
Install koshi on Linux, macOS, or Windows with Homebrew, Scoop, the release script, or from source.
koshi ships prebuilt binaries for Linux, macOS, and Windows on x86-64 and ARM64. Pick one method below.
macOS
With Homebrew:
brew install gohyuhan/koshi/koshiHomebrew adds the koshi tap during installation. Upgrade koshi along with your other outdated packages:
brew update
brew upgradeOr upgrade only koshi:
brew upgrade koshiWith the release script:
curl --proto "=https" --tlsv1.2 -sSfL \
https://github.com/gohyuhan/koshi/releases/latest/download/install.sh | bashLinux
curl --proto "=https" --tlsv1.2 -sSfL \
https://github.com/gohyuhan/koshi/releases/latest/download/install.sh | bashWindows
With PowerShell:
powershell -c "irm https://github.com/gohyuhan/koshi/releases/latest/download/install.ps1 | iex"With Scoop:
scoop bucket add koshi https://github.com/gohyuhan/scoop-koshi
scoop install koshi/koshiUpgrade after refreshing Scoop:
scoop update
scoop update koshiFrom source
Building needs Rust 1.96.
git clone https://github.com/gohyuhan/koshi.git
cd koshi
cargo build --release
./target/release/koshiUpdating in place
koshi updatekoshi update installs the newer release the way koshi was installed: through
brew for a Homebrew install, and by replacing the program file for a Scoop or
release script install. It then restarts each running session into the
installed build, keeping its panes, the programs in them, and their scrollback,
and an attached terminal rejoins on its own. A session that refuses the restart
is named on standard error and keeps the old build until you end it and start
it again.
scoop update koshi skips koshi while any koshi from that install runs; run
koshi update instead. After a plain brew upgrade, each running session
restarts into the new koshi at the next koshi command that reaches it.
koshi server-version # which build each running server runsSee Update and versions.
Check the installation
koshi doctorOne row per check — config, shell, terminal, directories, session log file,
router, session directory, and remote access — each rated ok, warn, or fail. See
Doctor.
Removing koshi later takes more than deleting the binary — config, logs, cache, and runtime files live outside the install directory. See Uninstall.