Repository navigation
v0.1.0
First tagged release of the fork, based on upstream Crush as of 2026-10-15.
Added
crush trust,crush trust --listandcrush trust --revoke: a trust gate
that keeps a cloned project'scrush.json,crushrc,.crush/and
OpenCode config inert until you say so.CRUSH_TRUST_PROJECT=1and
options.trusted_pathsare the non-interactive equivalents.- OpenCode import: MCP servers, providers, model choices, the cached
models.dev catalog, rules, skills, custom commands (opencode:<name>),
tool toggles, deny permissions,edit: allowandcompaction.autoare
read from a local OpenCode install.crush opencodeprints exactly what
was imported and why anything was skipped. Toggle pieces in
options.opencode;CRUSH_DISABLE_OPENCODE=1turns it all off. permissions allow-in-project edit write …(permissions.project_allowed_tools)
lets file tools skip the prompt only inside the project directory.option web-tools true/options.enable_web_tools/CRUSH_ENABLE_WEB_TOOLS
to opt in to thefetch,agentic_fetch,downloadandsourcegraphtools.- The import report flags MCP servers that fetch packages on start (
npx,
bunx,pnpm dlx,yarn dlx,@latest). - Windows, macOS and Linux release archives with
SHA256SUMS.txt, built by
thereleaseworkflow as a draft GitHub release.
Changed
- The provider catalog is offline by default; refresh it only with
crush update-providers. - Bash auto-approval only applies to a single parsed read-only command.
Wrappers (env,timeout, …), redirections, pipes and multi-line commands
always ask.envdumps,ps eandlsoutside the working directory ask too. - Every web tool call and every
agentic_fetchsub-agent request asks for
permission first;sourcegraphasks before each search. duandgit blamecan no longer read files outside the project.- Banned shell commands are also caught when hidden behind wrappers or paths.
- Config and lock directories are created readable only by the user, and the
server's unix socket is private to its owner. - Panic logs go to the log directory instead of the working directory.
crush --versionprefers the version passed at build time over the Go
toolchain's VCS stamp.
Removed
- PostHog telemetry and machine-id tracking.
- The startup update check.
- The Charm Hyper provider and the Catwalk/Hyper catalog fetches at startup.
- Automatic
.envloading, the forced Termux DNS resolvers and the global
pprof mux. - Upstream release, CLA and labeler automation.
Security
- Provider API keys are scrubbed from the agent's shell environment.
- Credential headers and key-like query parameters are redacted from HTTP
debug logs; env values that fail to resolve are no longer logged. - The
downloadtool caps writes at 100 MiB and removes oversized files. - The lint workflow no longer persists checkout credentials.
Downloads
| Platform | File |
|---|---|
| Windows x64 installer (recommended) | crush_0.1.0_Windows_x86_64_Setup.exe |
| Windows ARM64 installer | crush_0.1.0_Windows_arm64_Setup.exe |
| Windows x64 (portable zip) | crush_0.1.0_Windows_x86_64.zip |
| Windows ARM64 (portable zip) | crush_0.1.0_Windows_arm64.zip |
| macOS Apple silicon | crush_0.1.0_Darwin_arm64.tar.gz |
| macOS Intel | crush_0.1.0_Darwin_x86_64.tar.gz |
| Linux x64 | crush_0.1.0_Linux_x86_64.tar.gz |
| Linux ARM64 | crush_0.1.0_Linux_arm64.tar.gz |
The Windows installer needs no admin rights: it installs to
%LOCALAPPDATA%\Programs\Crush, adds crush to your PATH, adds a
Start menu entry, and uninstalls from Settings > Apps.
Verify a download against SHA256SUMS.txt:
shasum -a 256 -c SHA256SUMS.txt --ignore-missing (macOS/Linux) or
Get-FileHash crush_0.1.0_Windows_x86_64_Setup.exe (PowerShell).