Skip to content

Releases: charmbracelet/crush

nightly

24 Dec 01:01

Choose a tag to compare

nightly Pre-release
Pre-release

Verifying the artifacts

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//checksums.txt'
wget 'https://github.com/charmbracelet/crush/releases/download//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!

The Charm logo

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

v0.29.1

22 Dec 18:36
v0.29.1
adbfe9e

Choose a tag to compare

Mini Attachments Patch

This is tiny update to improve the behavior when files are dragged and dropped into Crush, and when long blocks of text are pasted in.

Hope you're chilling out! 💘

Changelog

Fixed


Verifying the artifacts

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.29.1/checksums.txt'
wget 'https://github.com/charmbracelet/crush/releases/download/v0.29.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!

The Charm logo

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

v0.29.0

19 Dec 19:51
v0.29.0
d6329f6

Choose a tag to compare

Paste, drag ’n drop, and other things from Xerox Parc

How's it going? We just added support for dragging and pasting attachments of all kinds into Crush, in an effort to make Crush your favorite desktop app in the terminal. We also added support to treat big pieces of pasted text as attachments.

Oh, and we also fixed a handful of bugs.

Hope you're staying warm (unless you're in the southern hemisphere, in which case, stay cool). See you soon and thanks for all the support! 🎁

Changelog

New!

Fixed


Verifying the artifacts

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.29.0/checksums.txt'
wget 'https://github.com/charmbracelet/crush/releases/download/v0.29.0/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!

The Charm logo

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

v0.28.0

18 Dec 21:18
v0.28.0
1cc3f88

Choose a tag to compare

Onboarding Stuff

This release is mostly to improve and fix the onboarding flow:

  • Fixed a bug that made impossible to type c on onboarding (model filter and API key input). Oops!
  • It's now possible to properly login to Hyper and/or GitHub Copilot via the onboarding flow.

See ya! 🎁 🎄

Changelog

New!

Fixed

Other stuff


Verifying the artifacts

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.28.0/checksums.txt'
wget 'https://github.com/charmbracelet/crush/releases/download/v0.28.0/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!

The Charm logo

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

v0.27.0

17 Dec 19:04
v0.27.0
3221de2

Choose a tag to compare

GitHub Copilot

It's almost the new year. Some people are celebrating things. In some places it's snowing. In other places it’s summertime.

🎁 Whatever’s going on for you, we have a little gift. The gift of Github Copilot auth in Crush.

Copilot should work automatically if you have already logged in your machine, otherwise, you'll be prompted to login once you choose a Copilot model. crush login copilot is also an option to login.

Enjoy!
Charm 💇🏻‍♀️

Screenshot 2025-12-17 at 11 27 37

Changelog

New!

Other stuff


Verifying the artifacts

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.27.0/checksums.txt'
wget 'https://github.com/charmbracelet/crush/releases/download/v0.27.0/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!

The Charm logo

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

v0.26.0

16 Dec 20:03
v0.26.0
27559b1

Choose a tag to compare

CCC: Carlos Crushes Code

This is primarily a maintenance release to move some things and around, update packages, and prep some stuff for the future. Special thanks to @caarlos0 (and @aymanbagabas!) for pushing Charm™ future-facing tech and infrastructure.

Huh?

Changelog

New!

Fixed

Other stuff


Verifying the artifacts

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.26.0/checksums.txt'
wget 'https://github.com/charmbracelet/crush/releases/download/v0.26.0/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!

The Charm logo

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

v0.25.0

16 Dec 14:41
v0.25.0
7c0d68d

Choose a tag to compare

Project tracking ’n’ bug fixes

This release introduces a new crush projects command that you can use to see all the projects where you used Crush that it knows about. Keep in mind that you need to start Crush at least once, with this new release, to get it recognized. It was primarily designed for programmatic use (see the --json flag, but maybe people will like it too). For details see crush projects --help).

We're also shipping some important bug fixes, including a patch for a possible broken session that could occur when OpenAI-compatible providers like Grok if you interrupted the model while it was thinking.

Keep crushing it! 💘

Changelog

New!

Fixed

Deps

Other stuff


Verifying the artifacts

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.25.0/checksums.txt'
wget 'https://github.com/charmbracelet/crush/releases/download/v0.25.0/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!

The Charm logo

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

v0.24.0

12 Dec 20:41
v0.24.0
dba25e7

Choose a tag to compare

To-Dos and More!

At last to-dos! We also made some improved noninteractive Crush and hardened things all around. Read on!

To-Dos

Apparently, LLMs are just like people: they need a to-do list to get anything useful done. That why we’ve finally granted Crush a first class to-do list, Charm-style. Now Crush will create to-dos list as-needed for better execution on tasks.

Does this mean that (with the right MCP) you can use Crush for grocery shopping? Why the heck not.

U so Fancy, Crush Run

There are a lot of people using Crush in sneaky places with its non-interacive (and super yolo) mode: crush run. As true command line connoisseurs, we've upgraded crush run to support output redirection (or pipes, if you will).

cat Taskfile | crush run "add descriptions please"
crush run "Summarize this project" > summary.md
crush run "Rate my Pokémon collection" < Pokedex.md > Pokerating.md

Bugz

We and the community crushed a bunch around rendering (thanks @aymanbagabas!), user interface (thanks @dawndiy!), and tools (thanks @Gustave-241021!).

That's all for now, but we have lots more on the way. Enjoy your weekend and maybe eat a burger. 🍔

—Charm 💋

Changelog

New!

Fixed

Other stuff


Verifying the artifacts

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.24.0/checksums.txt'
wget 'https://github.com/charmbracelet/crush/releases/download/v0.24.0/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!

The Charm logo

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

v0.23.0

11 Dec 20:15
v0.23.0
a15cf46

Choose a tag to compare

GPT 5.2 is here! ✨

OpenAI just released GPT 5.2 and Crush already supports it. Enjoy!

We also added GPT 5.1 Codex Max, which was missing until today. And of course, star contributors @Amolith is back with some nice small additions.

More good stuff coming soon! 💘

Changelog

New!

Other stuff


Verifying the artifacts

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.23.0/checksums.txt'
wget 'https://github.com/charmbracelet/crush/releases/download/v0.23.0/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!

The Charm logo

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

v0.22.2

10 Dec 13:32
v0.22.2
ee5e50a

Choose a tag to compare

Long Sesh in Claude Max? No problem.

This release improves how Crush refresh tokens from Claude Code or API key templates. It'll now automatically refresh when it expires and continue transparently. This affected long session only (8+ hours), and was only partially working until now. Kudos to @taciturnaxolotl for reporting and helping with this fix!

Additionally, @taigrr made a change to sort sessions by activity instead of creation on the dialog opened by ctrl+s.

@meowgorithm also fixed the need to press ctrl+c twice to close crush run. Pressing a single time will now work.

Happy coding! 🎄

Changelog

Fixed

Other stuff


Verifying the artifacts

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.22.2/checksums.txt'
wget 'https://github.com/charmbracelet/crush/releases/download/v0.22.2/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!

The Charm logo

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