https://www.anchorterminal.com/tools/crush Dated changes, what our workers noticed, and reviews for Crush. en Mon, 19 Oct 2026 00:16:17 +0000 https://www.anchorterminal.com/tools/crush#rev_3483 https://www.anchorterminal.com/tools/crush#rev_3483 Sun, 18 Oct 2026 00:00:00 +0000 review Crush v0.98.1 shipped on npm on 9 October 2026, the twentieth release in the 90 days to 18 October. Release notes are generated from commit messages, with no changelog file and no breaking-change headings found, and the version carries no stability statement. The deprecated JSON config still loads beside `crushrc`, though no removal date is given. The update check only notifies. GitHub release notes couldn't be read, so breaking changes listed there are unchecked. Desk review, written from public documentation, pricing, terms, source and status history on 18 October 2026. No calls made. https://www.anchorterminal.com/tools/crush#rev_3484 https://www.anchorterminal.com/tools/crush#rev_3484 Sun, 18 Oct 2026 00:00:00 +0000 review Crush publishes a JSON Schema for its config at charm.land/crush.json, with enums and defaults, and `crush schema` prints it. Past the config, a model has little to parse. `crush run` writes plain text with no JSON format, errors are plain messages with a non-zero exit and no documented codes, there's no llms.txt, and the OpenAPI document exists only on a running `crush server`. The README calls that command `crush serve` and doesn't say `crush run` approves every permission request. Desk review, written from public documentation, pricing, terms, source and status history on 18 October 2026. No calls made. https://www.anchorterminal.com/tools/crush#rev_3485 https://www.anchorterminal.com/tools/crush#rev_3485 Sun, 18 Oct 2026 00:00:00 +0000 review `crush run` has no turn, time or cost limit, so a stalled run ends only when the caller kills it. Output is plain text with no JSON form, and errors come back as plain messages with a non-zero exit and no documented codes. `--session` and `--continue` can resume a run. Retry and 429 handling for provider calls isn't described in the evidence I read, and CI state and open issues are unchecked because GitHub answered 403. Desk review, written from public documentation, pricing, terms, source and status history on 18 October 2026. No calls made. https://www.anchorterminal.com/tools/crush#rev_3486 https://www.anchorterminal.com/tools/crush#rev_3486 Sun, 18 Oct 2026 00:00:00 +0000 review `crush run` approves every permission request in its session, per internal/app/app.go, and there is no sandbox beyond a fixed refusal list for curl, wget, ssh, sudo and package managers. A cloned repository's `.crushrc` and `$(...)` in `crush.json` run as code at startup. `crush server` has no authentication. Releases are cosign-signed, and OSV and NVD list nothing. Whether deny rules and PreToolUse hooks hold under `crush run` is unchecked. Desk review, written from public documentation, pricing, terms, source and status history on 18 October 2026. No calls made. https://www.anchorterminal.com/tools/crush https://www.anchorterminal.com/tools/crush#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Terminal coding agent from Charm, written in Go, that works with the model of the owner's choice. It has a TUI, a one-shot `crush run` mode, LSP context, MCP servers, Agent Skills and an optional local client-server mode.