Skip to content
C

Crush v0.93.1

Released · Charm

What the release notes say

Disable mouse support + more

Hey, how's your week going? We have a few changes today, including mostly fixes but also a few nice additions.

Disable mouse support

Want to disable mouse support in Crush? Feel lucky because our favorite contributor @timotheosh added just that.

With the config below you can achieve that. It's also possible to toggle it via the command palette dialog.

crushrc:

option ui mouse false

crush.json:

{ "options": { "tui": { "mouse": false } } }
<img width="600" alt="image" src="https://github.com/user-attachments/assets/ad64e680-d244-4e7e-9cb4-1b7fff6271ed" /> <img width="600" alt="image" src="https://github.com/user-attachments/assets/a2fd43cd-bb46-4326-93cf-596e5361d77d" />

Fixed UX for non-vision models

In some cases, Crush were allowing you to attach an image even when the selected model was not vision-capable. The attachment was then being silent dropped in the request.

Now, we're properly validating it and showing a message so you know when it's not supported.

Fixed some models on GitHub Copilot

On Copilot some models only works on the /responses endpoint: named GPT-6 Astra and the Grok models.

Fixed some models on OpenCode Zen & Go

OpenCode also require some models to use specific endpoints. Not every model support the /chat/completions endpoint; some require /responses or /messages.

We fixed this issue for the models OpenCode currently supports.

Fixed Sentry MCP + others

A misconfiguration made it impossible to authenticate with OAuth2 with a few the MCPs, including the Sentry MCP. This is now fixed!

Fixed potential memory leak

@caniko discovered a memory leak, specifically when discover_models: true is set. This issue was fixed!

To read the technical explanation, see #3162 and #3683.


See you in the next release! The Charm Team :tm:

Changelog


<details> <summary>Verifying the artifacts</summary>

First, download the checksums.txt file and the checksums.txt.sigstore.json file files, for example, with wget:

wget 'https://github.com/charmbracelet/crush/releases/download/v0.93.1/checksums.txt'
wget 'https://github.com/charmbracelet/crush/releases/download/v0.93.1/checksums.txt.sigstore.json'

Then, verify it using cosign:

cosign verify-blob \
  --certificate-identity 'https://github.com/charmbracelet/meta/.github/workflows/goreleaser.yml@refs/heads/main' \
  --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
  --bundle 'checksums.txt.sigstore.json' \
  ./checksums.txt

If the output is Verified OK, you can safely use it to verify the checksums of other artifacts you downloaded from the release using sha256sum:

sha256sum --ignore-missing -c checksums.txt

Done! You artifacts are now verified!

</details>

<a href="https://charm.land/"><img alt="The Charm logo" src="https://stuff.charm.sh/charm-banner-next.jpg" width="400"></a>

Thoughts? Questions? We love hearing from you. Feel free to reach out on X, Discord, Slack, [The