npm
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.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, notinstall.sh. It supports x64 only.
curl.exe:
Install a specific version
Use this in Dockerfiles and CI, so every build gets the same Capy. Each release publishes its owninstall.sh with that version’s checksums. Run it from the release URL:
CAPY_VERSION on the installer:
npm install -g @capysc/cli@<version>.
Remove the standalone binary
Delete thecapy 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.