Crush
Overview
Version & Lifecycle
Community Notes
Crush install and provider-key deployment note
For managed Crush deployments, separate the installer choice from provider configuration. The upstream project documents multiple install channels; whichever source you package, validate the installed crush command and version in the same user or system context where it will run.
For unattended or pre-seeded lab images, avoid depending on the first-run API-key prompt. Crush reads provider keys from environment variables such as ANTHROPIC_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY, and OPENROUTER_API_KEY. Configure those at the user, shell, or device-management layer appropriate for your deployment and avoid baking personal keys into shared images.
Source: Charmbracelet Crush README.
Release Notes & Updates
Help us match vulnerabilities
No vulnerability match yet. Pick the right product:
Don’t see it? Paste a CPE
Also known as
Other names people use for this app — helps search and matching.
Sign in to suggest a name.
Packaging Notes
Available via Homebrew, NPM, Arch Linux, Nix, Debian/Ubuntu apt repo, Winget, Scoop, and Go install
