Skip to main content

​
Requirements

​
Install with npm

Verify the install:
Expected output:

​
Permission errors

If you see EACCES or “permission denied” errors during install:
  • macOS / Linux — prefix the command with sudo
  • Windows — open your terminal as Administrator

​
Alternative package managers

​
Updating the CLI

Install the latest version over the existing one:
Or pin a specific version:

​
Uninstalling

This removes the binary but does not delete your stored credentials. To fully remove Krypt from your system:

​
CLI configuration

After running krypt login, the CLI stores config at ~/.krypt/config.json with 0600 permissions (owner-only read/write):
Override the API URL with the KRYPT_API_URL environment variable — useful for self-hosted deployments or testing:
In each project directory, krypt init creates a .krypt file linking that folder to a Krypt project:

​
Troubleshooting

“krypt: command not found” Your npm global bin directory is not in your PATH. Run npm config get prefix and add <prefix>/bin to your shell profile. See the npm docs on resolving global install issues. “Cannot find module” errors Reinstall with --force to rebuild native dependencies:
Network errors during install If you’re behind a corporate proxy, configure npm to use it:
See the npm proxy configuration docs.

​
Next steps

  • Quickstart — push your first secret in 5 minutes
  • CLI commands — full reference for every command and flag