v0.25.0

# 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!
* 4b86d090392a761106d4b33b2937e183af62bcd6: feat: add centralized project tracking (for Splitrail) (#1553) (@mike1858)
### Fixed
* a2678eb4c642faf52e5496da9af1ad94d847a336: fix(uiutil): add Cursor interface (@aymanbagabas)
* 9ca655702eaebdbc058a11361c2af9968689516a: fix: typo in Subscriber type name (#1616) (@meowgorithm)
* 33d8aafb54b884f2bbcea4f1b21e75cd850c6007: fix: update fantasy with fix for empty messages bug (#1639) (@andreynering)
* c822651c9bfe6071fe6d29c1f470c9221faf0613: fix:remove 100MB file size limit from download tool (#1631) (@Gustave-241021)
### Deps
* a7d13872fe1ba8b6b3c8b1690583dbc74281e338: fix(deps): use charm.land glamour and log (#1469) (@caarlos0)
### Other stuff
* b1d93ebbadd2e3ec4d74015f3b8eeadbbc0b18cc: chore(ui): remove left padding in thinking blocks (#1629) (@meowgorithm)
* 69d3ac961bfccc36a1df5b3b680a7b67fb929b01: chore: search improvements (#1632) (@kujtimiihoxha)
* 0d0ac7ce6776844e1bd2ad3e97bec67c14f3ad38: chore: send `interactive` attribute (for `crush run`) (#1635) (@andreynering)
* df6f35a694dd3e36ead0b985b996b45b9a68489d: refactor(tui): move UI message handling to internal/uiutil (@aymanbagabas)
* 7918c90ed0587dc67a178f6bd7884b6899387a63: refactor(tui): move command loading to uicmd package (@aymanbagabas)
* 31e155c2ce1a7a906c244d381daf15dd5481c5e7: refactor(tui): unify commandType definition (@aymanbagabas)

---

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

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

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