v0.50.0

# Catching up with `crush run`

Did you know that you can Crush in a non-interactive manner? It's easy as `crush run`.

```bash
crush run "what's the best tui framework for go?"
```

That’s been a thing for a while. Starting with this release you can pickup sessions non-interactively thanks to an awesome feature by @seroperson:

* `--continue` (`-C`): continue last session
* `--session` (`-s`): continue a specific session

```bash
# Continue a previous session
crush run --session {session-id} "um, can you repeat that?"

# Continue the most recent session
crush run --continue "tell me more"
```

How can you find your session ID? You can use the [session management commands we added 4 days ago](https://github.com/charmbracelet/crush/releases/tag/v0.48.0). In short:

```bash
# List all sessions (ordered by most recent)
crush session list

# Alternatively output JSON, useful for scripts, etc.
crush session list --json
```

The week is just started. See ya in a few!
Charm :sparkles:


## Changelog
### New!
* fad58e2c269654c052a768191cc7a3ec0af391e5: feat: be able to continue non-interactive sessions (#2401) (@seroperson)
### Fixed
* b05a4add77941265581e3508ce50429143e6a8fa: fix(ui): render nested tools consistently across states (@meowgorithm)
* efb52db17ed78f68bb7de7c79bd575263292642a: fix(vercel): fix validation of api keys for vercel (#2415) (@andreynering)
* c9efb207ea0575ca837e2d957738452da78b366b: fix: keep original order when filtering models (#2416) (@andreynering)
### Other stuff
* a1fc44bb0d851f240a345cf3a1c76d5a9f78a3d2: chore(events): add events for the CLI session series of commands (#2408) (@meowgorithm)
* 9a5a510e68619bc4cdb4131665306219b1995cb2: ci(labeler): add vercel label (@andreynering)
* 6e56a7f45acab2f19463ce69b29d13529ef81f35: lint: modernize new pointer creation (e.g. new(true)) (@meowgorithm)

---

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

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

```bash
wget 'https://github.com/charmbracelet/crush/releases/download/v0.50.0/checksums.txt'
wget 'https://github.com/charmbracelet/crush/releases/download/v0.50.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).