Skip to main content
Capy is one CLI. Pick the install that fits your machine.

npm

Or with Bun:
The npm package needs Node.js 18 or newer. On Windows, npm installs two launchers: capy.ps1 and capy.cmd. If PowerShell refuses to run capy because running scripts is disabled on the machine, run capy.cmd instead. The PowerShell installer below installs capy.exe, which has no launcher script.

Standalone installer (macOS and Linux)

No Node or npm needed.
The installer downloads the binary for your system from GitHub Releases and checks its SHA-256 before installing. It supports macOS and Linux on arm64 and x64. It needs curl or wget, tar, and sha256sum or shasum. If Capy is already installed as a standalone file, the installer replaces it in place. If Capy came from npm, the installer stops and nothing is changed: update with npm install -g @capysc/cli. For a new install it uses /usr/local/bin when that folder is on your PATH and writable, otherwise ~/.local/bin. CAPY_INSTALL_DIR sets the folder.

Windows PowerShell

Use the native PowerShell installer, not install.sh. It supports x64 only.
Or download and run it using Windows’ curl.exe:

Install a specific version

Use this in Dockerfiles and CI, so every build gets the same Capy. Each release publishes its own install.sh with that version’s checksums. Run it from the release URL:
Or set CAPY_VERSION on the installer:
For npm, install the version by name: npm install -g @capysc/cli@<version>.

Remove the standalone binary

Delete the capy file from the folder the installer printed. On Windows, delete capy.exe from that folder. The ~/.capy folder holds your keys: do not delete it to reinstall.

Next

Get started

Pick your runtime and sync your first secrets.
Last modified on November 20, 2026