v0.51.0

charmbracelet/crushv0.51.0Mar 19, 2026by github-actions[bot]

AI Summary

This release introduces a major Docker MCP Catalog integration, allowing Crush to dynamically load relevant MCPs during conversations. It also adds CLI ergonomics improvements including shortcuts for common commands and new flags for session management.

Key Highlights

  • Docker MCP Catalog integration - dynamically loads relevant MCPs on demand during conversations
  • CLI shortcuts: `crush r` for `crush run` and `crush s` for `crush session`
  • New `--session` and `--continue` flags for both CLI and TUI modes
  • Fix for Anthropic authentication via Google Vertex
  • Press ctrl+p in interactive mode to enable Docker MCP Catalog

New Features

  • Docker MCP integration - pulls in MCPs on demand (Postgres, robotics, ARM, etc.)
  • CLI aliases: `crush r` -> `crush run`, `crush s` -> `crush session`
  • `--continue` flag to resume last session in TUI or non-interactively
  • `--session` flag to open a specific session by ID
  • Fix for Anthropic authentication via Google Vertex

Full Release Notes

# Crush + Docker MCP :whale:

We teamed up with [Docker](https://www.docker.com/) to natively integrate the [Docker MCP Catalog](https://hub.docker.com/mcp) into Crush and—if we do say so ourselves—it rocks!

There are also some CLI improvements and bug fixes in this release, too. Let’s get to it!

## One MCP to Rule Them All

<p><img width="300" alt="image" src="https://github.com/user-attachments/assets/b6bb6fdd-e7c6-48aa-8a03-8971c08796c8" /></p>

As we were saying, the big feature in this release is an integration with the [Docker MCP Catalog](https://hub.docker.com/mcp).

During a conversation, Crush and Docker work together to pull in relevant MCPs on demand. Working with Postgres? Building a robot? Going deep on ARM? Crush and Docker will load in the MCP you need, when you need it (and yes, Crush will still ask for permission).

To get started, make sure Docker Desktop is running, then fire up Crush, press <kbd>ctrl+p</kbd>, choose “Enable Docker MCP Catalog”, and get to work.

For more info on this rad feature [check out the blog post](https://charm.land/blog/crush-and-docker-mcp/).

<img width="600" alt="image" src="https://github.com/user-attachments/assets/a532dac3-45a0-432d-9982-d79403b32cd2" />

## CLI Ergonomics

People love `crush run` and `crush session`. What they do not, love, however, is typing. We have a solution for this, behold!

* `crush run` -> `crush r`
* `crush session` -> `crush s`

We also added `--session` and `--continue` flags to `crush`, allowing you to quickly pick resume sessions in both the CLI and the TUI.

```bash
crush --continue     # continue the last session in the TUI
crush run --continue # continue the last session non-interactively
```

For more see `crush —help`.

These flags are now also available for the interactive mode, so you can just run `crush --continue` to automatically open the last chat, or `crush --session {session-id}` to automatically open a specific session.

## Anthropic + Vertex Fix

If you work at a big company you probably know all about burning your boss’s tokens freely. This release fixes an authentication issuewith Anthropic via Google Vertex allowing you to resume token burning For more info see https://github.com/charmbracelet/fantasy/pull/157.

Enjoy the release :whale:
Charm

## Changelog
### New!
* ddd99cd2f650adfa9dc9ec961365266d8512c4a0: feat: add aliases: `crush r` -> `crush run`, `crush s` -> `crush session` (#2424) (@andreynering)
* 630ff8c5dfeaabc96b8f05917d28455ad7e1075e: feat: add support for `--session` and `--continue` for the tui (#2422) (@andreynering)
* e0dcaba820b1a5f391fad9b89590e8c8932b6404: feat: docker mcp integration (#2026) (@kujtimiihoxha)
### Other stuff
* aa253c524ad789c0d0eccad57322b18ae469edbc: chore(taskfile): enhance `deps` task to work for recent releases (@andreynering)
* a3288de0d2a6b70aab1c1caa238f307a401b259f: chore: auto-update files (@charmcli)

---

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

First, download the [`checksums.txt` file](https://github.com/charmbracelet/crush/releases/download/v0.51.0/checksums.txt) and the [`checksums.txt.sigstore.json` file](https://github.com/charmbracelet/crush/releases/download/v0.51.0/checksums.txt.sigstore.json) files, for example, with `wget`:

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

Then, verify it using [`cosign`](https://github.com/sigstore/cosign):

```bash
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`:

```bash
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](https://x.com/charmcli), [Discord](https://charm.land/discord), [Slack](https://charm.land/slack), [The Fediverse](https://mastodon.social/@charmcli), [Bluesky](https://bsky.app/profile/charm.land).