v0.27.0

charmbracelet/crushv0.27.0Dec 17, 2025by github-actions[bot]

AI Summary

This release adds GitHub Copilot authentication support to Crush, allowing users to use Copilot models directly from the command-line shell. Users can authenticate automatically if already logged in, or use `crush login copilot` to login explicitly.

Key Highlights

GitHub Copilot authentication flow via TUI (terminal user interface)
GitHub Copilot support with model selection
Improved help text for the projects command
Auto-update files maintenance
Small refactoring adjustments in hyper

New Features

GitHub Copilot authentication via TUI (#1645)
GitHub Copilot support with model integration (#1645)
`crush login copilot` command for explicit authentication

Full Release Notes

# 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 💇🏻‍♀️

<img width="554" height="359" alt="Screenshot 2025-12-17 at 11 27 37" src="https://github.com/user-attachments/assets/e50f422a-d339-4784-906d-42e1be14c0e8" />

## Changelog
### New!
* 5fe017723303e8cdd40f4f14de9da46c911e761f: feat: add github copilot auth flow via tui (#1645) (@andreynering)
* ab057fdf04affbe4454d35741684277362a92095: feat: add github copilot support (#1645) (@andreynering, @marifcelik and @mikluko)
### Other stuff
* e67c16e6b34d47322a200a3e1a822e4b633f4732: chore(cmd/projects): improve help text (#1647) (@meowgorithm)
* 66a272d8b6054cfeba0d29157370f2dad90889b9: chore: auto-update files (@charmcli)
* 77e0475d2ba275cc930b111f8ef31a145b2d8619: chore: auto-update files (@charmcli)
* cddb306ab52dd6c24b11cb972def396a6a8e02ad: refactor(hyper): a couple of small adjustments (@andreynering)

---

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

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

```bash
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`](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).