v0.49.0

# Friday patch

Hope you had a great weekend! Here's a patch with some small fixes and improvements.

## No background

Added new command on the command palette (<kbd>ctrl+p</kbd>) to toggle on/off the background color (a.k.a. enable "transparent mode"). This will be persisted.

<details><summary>Screenshots</summary>

<img width="600" alt="image" src="https://github.com/user-attachments/assets/63ec34ec-40fc-4f9b-8159-4fb55f13f166" />

<img width="600" alt="image" src="https://github.com/user-attachments/assets/5c4dcc55-6b06-4d5a-ab36-149a9fa422ca" />

</details> 

## Easier Bedrock

If you use AWS Bedrock, you'll now be able to just paste your API key in the input as any other provider.

Before, it was working only via environment setup (`AWS_BEARER_TOKEN_BEDROCK` env or `aws login`).

## Updated OpenAI SDK from v2 to v3

Note that this SDK is used not only for OpenAI, but for any provider that is OpenAI compatible.

This might look like a technical detail, but it means we're covered with the latest bug fixes. A couple users confirmed this fixed some rare errors on some providers.

## `auto_background_after`

@portertech contributed by adding a new `auto_background_after` param to the Bash tool.

With this param, the model can ask Crush how many seconds it should wait before moving that command into a background job. Before it was always 60 seconds, which is still the current default.

Enjoy your weekend!
The Charm team :tm:

## Changelog
### New!
* f1bdb9c9b815f884b81e5b6bf810e74b8f5f48a6: feat: add configurable auto-background threshold for bash tool (#2183) (@portertech)
* eaa9a4a9bffb62a3adadc53986a51c033bece785: feat: allow to paste bedrock api keys (#2407) (@andreynering)
### Other stuff
* 81f2d3811970d823e7fbaa83d60d6ef1d6ad707d: chore(ui): add toggle for transparent bg to command palette (#2405) (@meowgorithm)
* 451faa7110d13931c60923889078340cec50df18: chore: update openai sdk to v3 (#2406) (@andreynering)

---

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

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

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