1**NOTE:** This is a personal fork of
2[Crush](https://github.com/charmbracelet/crush) where I'm experimenting with
3things. You'll also find my patches merged here before they're merged into
4upstream. I've also unconditionally disabled metrics and yote the CLA; devs
5shouldn't assign their copyrights to maintainers and hand them the rug they'll
6yank from under you later.
7
8Install my fork either…
9
10- Using [bin](https://github.com/marcosnils/bin) (highly recommended
11 because it's one tool to manage and update myriad CLI tools
12 distributed as statically-linked binaries, like _nasin pali_)
13 ```bash
14 bin install goinstall://git.secluded.site/crush@latest
15 ```
16- Or using the [go toolchain](https://go.dev/dl) (requires tracking updates
17 manually)
18 ```bash
19 go install git.secluded.site/crush@latest
20 ```
21
22I pull upstream changes into the `upstream` branch here, break my
23branches off that, then merge them into my `dev` branch, which gets
24rebased on `upstream` fairly often. `dev` history will get rewritten
25frequently.
26
27Contributions are welcome (see following section) and I'll try to
28maintain anything I accept here.
29
30## Contributions
31
32Patch requests are in [amolith/llm-projects] on [pr.pico.sh]. You don't
33need a new account to contribute, you don't need to fork this repo, you
34don't need to fiddle with `git send-email`, you don't need to faff with
35your email client to get `git request-pull` working...
36
37You just need:
38
39- Git
40- SSH
41- An SSH key
42
43```sh
44# Clone this repo, make your changes, and commit them
45# Create a new patch request with
46git format-patch origin/main --stdout | ssh pr.pico.sh pr create amolith/llm-projects
47# After potential feedback, submit a revision to an existing patch request with
48git format-patch origin/main --stdout | ssh pr.pico.sh pr add {prID}
49# List patch requests
50ssh pr.pico.sh pr ls amolith/llm-projects
51```
52
53See "How do Patch Requests work?" on [pr.pico.sh]'s home page for a more
54complete example workflow.
55
56[amolith/llm-projects]: https://pr.pico.sh/r/amolith/llm-projects
57[pr.pico.sh]: https://pr.pico.sh
58
59---
60
61_Everything from here on is from the original Crush README._
62
63---
64
65# Crush
66
67<p align="center">
68 <a href="https://stuff.charm.sh/crush/charm-crush.png"><img width="450" alt="Charm Crush Logo" src="https://github.com/user-attachments/assets/adc1a6f4-b284-4603-836c-59038caa2e8b" /></a><br />
69 <a href="https://github.com/charmbracelet/crush/releases"><img src="https://img.shields.io/github/release/charmbracelet/crush" alt="Latest Release"></a>
70 <a href="https://github.com/charmbracelet/crush/actions"><img src="https://github.com/charmbracelet/crush/actions/workflows/build.yml/badge.svg" alt="Build Status"></a>
71</p>
72
73<p align="center">Your new coding bestie, now available in your favourite terminal.<br />Your tools, your code, and your workflows, wired into your LLM of choice.</p>
74<p align="center">你的新编程伙伴，现在就在你最爱的终端中。<br />你的工具、代码和工作流，都与您选择的 LLM 模型紧密相连。</p>
75
76<p align="center"><img width="800" alt="Crush Demo" src="https://github.com/user-attachments/assets/58280caf-851b-470a-b6f7-d5c4ea8a1968" /></p>
77
78## Features
79
80- **Multi-Model:** choose from a wide range of LLMs or add your own via OpenAI- or Anthropic-compatible APIs
81- **Flexible:** switch LLMs mid-session while preserving context
82- **Session-Based:** maintain multiple work sessions and contexts per project
83- **LSP-Enhanced:** Crush uses LSPs for additional context, just like you do
84- **Extensible:** add capabilities via MCPs (`http`, `stdio`, and `sse`)
85- **Works Everywhere:** first-class support in every terminal on macOS, Linux, Windows (PowerShell and WSL), FreeBSD, OpenBSD, and NetBSD
86
87## Installation
88
89Use a package manager:
90
91```bash
92# Homebrew
93brew install charmbracelet/tap/crush
94
95# NPM
96npm install -g @charmland/crush
97
98# Arch Linux (btw)
99yay -S crush-bin
100
101# Nix
102nix run github:numtide/nix-ai-tools#crush
103```
104
105Windows users:
106
107```bash
108# Winget
109winget install charmbracelet.crush
110
111# Scoop
112scoop bucket add charm https://github.com/charmbracelet/scoop-bucket.git
113scoop install crush
114```
115
116<details>
117<summary><strong>Nix (NUR)</strong></summary>
118
119Crush is available via [NUR](https://github.com/nix-community/NUR) in `nur.repos.charmbracelet.crush`.
120
121You can also try out Crush via `nix-shell`:
122
123```bash
124# Add the NUR channel.
125nix-channel --add https://github.com/nix-community/NUR/archive/main.tar.gz nur
126nix-channel --update
127
128# Get Crush in a Nix shell.
129nix-shell -p '(import <nur> { pkgs = import <nixpkgs> {}; }).repos.charmbracelet.crush'
130```
131
132### NixOS & Home Manager Module Usage via NUR
133
134Crush provides NixOS and Home Manager modules via NUR.
135You can use these modules directly in your flake by importing them from NUR. Since it auto detects whether its a home manager or nixos context you can use the import the exact same way :)
136
137```nix
138{
139 inputs = {
140 nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
141 nur.url = "github:nix-community/NUR";
142 };
143
144 outputs = { self, nixpkgs, nur, ... }: {
145 nixosConfigurations.your-hostname = nixpkgs.lib.nixosSystem {
146 system = "x86_64-linux";
147 modules = [
148 nur.modules.nixos.default
149 nur.repos.charmbracelet.modules.crush
150 {
151 programs.crush = {
152 enable = true;
153 settings = {
154 providers = {
155 openai = {
156 id = "openai";
157 name = "OpenAI";
158 base_url = "https://api.openai.com/v1";
159 type = "openai";
160 api_key = "sk-fake123456789abcdef...";
161 models = [
162 {
163 id = "gpt-4";
164 name = "GPT-4";
165 }
166 ];
167 };
168 };
169 lsp = {
170 go = { command = "gopls"; enabled = true; };
171 nix = { command = "nil"; enabled = true; };
172 };
173 options = {
174 context_paths = [ "/etc/nixos/configuration.nix" ];
175 tui = { compact_mode = true; };
176 debug = false;
177 };
178 };
179 };
180 }
181 ];
182 };
183 };
184}
185```
186
187</details>
188
189<details>
190<summary><strong>Debian/Ubuntu</strong></summary>
191
192```bash
193sudo mkdir -p /etc/apt/keyrings
194curl -fsSL https://repo.charm.sh/apt/gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/charm.gpg
195echo "deb [signed-by=/etc/apt/keyrings/charm.gpg] https://repo.charm.sh/apt/ * *" | sudo tee /etc/apt/sources.list.d/charm.list
196sudo apt update && sudo apt install crush
197```
198
199</details>
200
201<details>
202<summary><strong>Fedora/RHEL</strong></summary>
203
204```bash
205echo '[charm]
206name=Charm
207baseurl=https://repo.charm.sh/yum/
208enabled=1
209gpgcheck=1
210gpgkey=https://repo.charm.sh/yum/gpg.key' | sudo tee /etc/yum.repos.d/charm.repo
211sudo yum install crush
212```
213
214</details>
215
216Or, download it:
217
218- [Packages][releases] are available in Debian and RPM formats
219- [Binaries][releases] are available for Linux, macOS, Windows, FreeBSD, OpenBSD, and NetBSD
220
221[releases]: https://github.com/charmbracelet/crush/releases
222
223Or just install it with Go:
224
225```
226go install github.com/charmbracelet/crush@latest
227```
228
229> [!WARNING]
230> Productivity may increase when using Crush and you may find yourself nerd
231> sniped when first using the application. If the symptoms persist, join the
232> [Discord][discord] and nerd snipe the rest of us.
233
234## Getting Started
235
236The quickest way to get started is to grab an API key for your preferred
237provider such as Anthropic, OpenAI, Groq, or OpenRouter and just start
238Crush. You'll be prompted to enter your API key.
239
240That said, you can also set environment variables for preferred providers.
241
242| Environment Variable | Provider |
243| --------------------------- | -------------------------------------------------- |
244| `ANTHROPIC_API_KEY` | Anthropic |
245| `OPENAI_API_KEY` | OpenAI |
246| `OPENROUTER_API_KEY` | OpenRouter |
247| `GEMINI_API_KEY` | Google Gemini |
248| `CEREBRAS_API_KEY` | Cerebras |
249| `HF_TOKEN` | Huggingface Inference |
250| `VERTEXAI_PROJECT` | Google Cloud VertexAI (Gemini) |
251| `VERTEXAI_LOCATION` | Google Cloud VertexAI (Gemini) |
252| `GROQ_API_KEY` | Groq |
253| `AWS_ACCESS_KEY_ID` | AWS Bedrock (Claude) |
254| `AWS_SECRET_ACCESS_KEY` | AWS Bedrock (Claude) |
255| `AWS_REGION` | AWS Bedrock (Claude) |
256| `AWS_PROFILE` | AWS Bedrock (Custom Profile) |
257| `AWS_BEARER_TOKEN_BEDROCK` | AWS Bedrock |
258| `AZURE_OPENAI_API_ENDPOINT` | Azure OpenAI models |
259| `AZURE_OPENAI_API_KEY` | Azure OpenAI models (optional when using Entra ID) |
260| `AZURE_OPENAI_API_VERSION` | Azure OpenAI models |
261
262### By the Way
263
264Is there a provider you’d like to see in Crush? Is there an existing model that needs an update?
265
266Crush’s default model listing is managed in [Catwalk](https://github.com/charmbracelet/catwalk), a community-supported, open source repository of Crush-compatible models, and you’re welcome to contribute.
267
268<a href="https://github.com/charmbracelet/catwalk"><img width="174" height="174" alt="Catwalk Badge" src="https://github.com/user-attachments/assets/95b49515-fe82-4409-b10d-5beb0873787d" /></a>
269
270## Configuration
271
272Crush runs great with no configuration. That said, if you do need or want to
273customize Crush, configuration can be added either local to the project itself,
274or globally, with the following priority:
275
2761. `.crush.json`
2772. `crush.json`
2783. `$HOME/.config/crush/crush.json`
279
280Configuration itself is stored as a JSON object:
281
282```json
283{
284 "this-setting": { "this": "that" },
285 "that-setting": ["ceci", "cela"]
286}
287```
288
289As an additional note, Crush also stores ephemeral data, such as application state, in one additional location:
290
291```bash
292# Unix
293$HOME/.local/share/crush/crush.json
294
295# Windows
296%LOCALAPPDATA%\crush\crush.json
297```
298
299### LSPs
300
301Crush can use LSPs for additional context to help inform its decisions, just
302like you would. LSPs can be added manually like so:
303
304```json
305{
306 "$schema": "https://charm.land/crush.json",
307 "lsp": {
308 "go": {
309 "command": "gopls",
310 "env": {
311 "GOTOOLCHAIN": "go1.24.5"
312 }
313 },
314 "typescript": {
315 "command": "typescript-language-server",
316 "args": ["--stdio"]
317 },
318 "nix": {
319 "command": "nil"
320 }
321 }
322}
323```
324
325### MCPs
326
327Crush also supports Model Context Protocol (MCP) servers through three
328transport types: `stdio` for command-line servers, `http` for HTTP endpoints,
329and `sse` for Server-Sent Events. Environment variable expansion is supported
330using `$(echo $VAR)` syntax.
331
332```json
333{
334 "$schema": "https://charm.land/crush.json",
335 "mcp": {
336 "filesystem": {
337 "type": "stdio",
338 "command": "node",
339 "args": ["/path/to/mcp-server.js"],
340 "timeout": 120,
341 "disabled": false,
342 "env": {
343 "NODE_ENV": "production"
344 }
345 },
346 "github": {
347 "type": "http",
348 "url": "https://api.githubcopilot.com/mcp/",
349 "timeout": 120,
350 "disabled": false,
351 "headers": {
352 "Authorization": "Bearer $GH_PAT"
353 }
354 },
355 "streaming-service": {
356 "type": "sse",
357 "url": "https://example.com/mcp/sse",
358 "timeout": 120,
359 "disabled": false,
360 "headers": {
361 "API-Key": "$(echo $API_KEY)"
362 }
363 }
364 }
365}
366```
367
368### Memory
369
370Crush automatically includes two memory files for cross-project instructions.
371
372- `~/.config/crush/CRUSH.md`: Crush-specific rules that would confuse other
373 agentic coding tools. If you only use Crush, this is the only one you need to
374 edit.
375- `~/.config/AGENTS.md`: generic instructions that other coding tools might
376 read. Avoid referring to Crush-specific tools or workflows here.
377
378You can customize these paths using the `memory_paths` option in your
379configuration:
380
381```json
382{
383 "$schema": "https://charm.land/crush.json",
384 "options": {
385 "memory_paths": [
386 "/path/to/custom/memory/file.md",
387 "/path/to/folder/of/files/" // recursively load all .md files in folder
388 ]
389 }
390}
391```
392
393### Ignoring Files
394
395Crush respects `.gitignore` files by default, but you can also create a
396`.crushignore` file to specify additional files and directories that Crush
397should ignore. This is useful for excluding files that you want in version
398control but don't want Crush to consider when providing context.
399
400The `.crushignore` file uses the same syntax as `.gitignore` and can be placed
401in the root of your project or in subdirectories.
402
403### Allowing Tools
404
405By default, Crush will ask you for permission before running tool calls. If
406you'd like, you can allow tools to be executed without prompting you for
407permissions. Use this with care.
408
409```json
410{
411 "$schema": "https://charm.land/crush.json",
412 "permissions": {
413 "allowed_tools": [
414 "view",
415 "ls",
416 "grep",
417 "edit",
418 "mcp_context7_get-library-doc"
419 ]
420 }
421}
422```
423
424You can also skip all permission prompts entirely by running Crush with the
425`--yolo` flag. Be very, very careful with this feature.
426
427### Initialization
428
429When you initialize a project, Crush analyzes your codebase and creates
430a context file that helps it work more effectively in future sessions.
431By default, this file is named `AGENTS.md`, but you can customize the
432name and location with the `initialize_as` option:
433
434```json
435{
436 "$schema": "https://charm.land/crush.json",
437 "options": {
438 "initialize_as": "AGENTS.md"
439 }
440}
441```
442
443This is useful if you prefer a different naming convention or want to
444place the file in a specific directory (e.g., `CRUSH.md` or
445`docs/LLMs.md`). Crush will fill the file with project-specific context
446like build commands, code patterns, and conventions it discovered during
447initialization.
448
449### Attribution Settings
450
451By default, Crush adds attribution information to Git commits and pull requests
452it creates. You can customize this behavior with the `attribution` option:
453
454```json
455{
456 "$schema": "https://charm.land/crush.json",
457 "options": {
458 "attribution": {
459 "trailer_style": "co-authored-by",
460 "generated_with": true
461 }
462 }
463}
464```
465
466- `trailer_style`: Controls the attribution trailer added to commit messages
467 (default: `assisted-by`)
468 - `assisted-by`: Adds `Assisted-by: [Model Name] via Crush <crush@charm.land>`
469 (includes the model name)
470 - `co-authored-by`: Adds `Co-Authored-By: Crush <crush@charm.land>`
471 - `none`: No attribution trailer
472- `generated_with`: When true (default), adds `💘 Generated with Crush` line to
473 commit messages and PR descriptions
474
475### Custom Providers
476
477Crush supports custom provider configurations for both OpenAI-compatible and
478Anthropic-compatible APIs.
479
480> [!NOTE]
481> Note that we support two "types" for OpenAI. Make sure to choose the right one
482> to ensure the best experience!
483> * `openai` should be used when proxying or routing requests through OpenAI.
484> * `openai-compat` should be used when using non-OpenAI providers that have OpenAI-compatible APIs.
485
486#### OpenAI-Compatible APIs
487
488Here’s an example configuration for Deepseek, which uses an OpenAI-compatible
489API. Don't forget to set `DEEPSEEK_API_KEY` in your environment.
490
491```json
492{
493 "$schema": "https://charm.land/crush.json",
494 "providers": {
495 "deepseek": {
496 "type": "openai-compat",
497 "base_url": "https://api.deepseek.com/v1",
498 "api_key": "$DEEPSEEK_API_KEY",
499 "models": [
500 {
501 "id": "deepseek-chat",
502 "name": "Deepseek V3",
503 "cost_per_1m_in": 0.27,
504 "cost_per_1m_out": 1.1,
505 "cost_per_1m_in_cached": 0.07,
506 "cost_per_1m_out_cached": 1.1,
507 "context_window": 64000,
508 "default_max_tokens": 5000
509 }
510 ]
511 }
512 }
513}
514```
515
516#### Anthropic-Compatible APIs
517
518Custom Anthropic-compatible providers follow this format:
519
520```json
521{
522 "$schema": "https://charm.land/crush.json",
523 "providers": {
524 "custom-anthropic": {
525 "type": "anthropic",
526 "base_url": "https://api.anthropic.com/v1",
527 "api_key": "$ANTHROPIC_API_KEY",
528 "extra_headers": {
529 "anthropic-version": "2023-06-01"
530 },
531 "models": [
532 {
533 "id": "claude-sonnet-4-20250514",
534 "name": "Claude Sonnet 4",
535 "cost_per_1m_in": 3,
536 "cost_per_1m_out": 15,
537 "cost_per_1m_in_cached": 3.75,
538 "cost_per_1m_out_cached": 0.3,
539 "context_window": 200000,
540 "default_max_tokens": 50000,
541 "can_reason": true,
542 "supports_attachments": true
543 }
544 ]
545 }
546 }
547}
548```
549
550### Amazon Bedrock
551
552Crush currently supports running Anthropic models through Bedrock, with caching disabled.
553
554- A Bedrock provider will appear once you have AWS configured, i.e. `aws configure`
555- Crush also expects the `AWS_REGION` or `AWS_DEFAULT_REGION` to be set
556- To use a specific AWS profile set `AWS_PROFILE` in your environment, i.e. `AWS_PROFILE=myprofile crush`
557- Alternatively to `aws configure`, you can also just set `AWS_BEARER_TOKEN_BEDROCK`
558
559### Vertex AI Platform
560
561Vertex AI will appear in the list of available providers when `VERTEXAI_PROJECT` and `VERTEXAI_LOCATION` are set. You will also need to be authenticated:
562
563```bash
564gcloud auth application-default login
565```
566
567To add specific models to the configuration, configure as such:
568
569```json
570{
571 "$schema": "https://charm.land/crush.json",
572 "providers": {
573 "vertexai": {
574 "models": [
575 {
576 "id": "claude-sonnet-4@20250514",
577 "name": "VertexAI Sonnet 4",
578 "cost_per_1m_in": 3,
579 "cost_per_1m_out": 15,
580 "cost_per_1m_in_cached": 3.75,
581 "cost_per_1m_out_cached": 0.3,
582 "context_window": 200000,
583 "default_max_tokens": 50000,
584 "can_reason": true,
585 "supports_attachments": true
586 }
587 ]
588 }
589 }
590}
591```
592
593### Local Models
594
595Local models can also be configured via OpenAI-compatible API. Here are two common examples:
596
597#### Ollama
598
599```json
600{
601 "providers": {
602 "ollama": {
603 "name": "Ollama",
604 "base_url": "http://localhost:11434/v1/",
605 "type": "openai-compat",
606 "models": [
607 {
608 "name": "Qwen 3 30B",
609 "id": "qwen3:30b",
610 "context_window": 256000,
611 "default_max_tokens": 20000
612 }
613 ]
614 }
615 }
616}
617```
618
619#### LM Studio
620
621```json
622{
623 "providers": {
624 "lmstudio": {
625 "name": "LM Studio",
626 "base_url": "http://localhost:1234/v1/",
627 "type": "openai-compat",
628 "models": [
629 {
630 "name": "Qwen 3 30B",
631 "id": "qwen/qwen3-30b-a3b-2507",
632 "context_window": 256000,
633 "default_max_tokens": 20000
634 }
635 ]
636 }
637 }
638}
639```
640
641## Logging
642
643Sometimes you need to look at logs. Luckily, Crush logs all sorts of
644stuff. Logs are stored in `./.crush/logs/crush.log` relative to the project.
645
646The CLI also contains some helper commands to make perusing recent logs easier:
647
648```bash
649# Print the last 1000 lines
650crush logs
651
652# Print the last 500 lines
653crush logs --tail 500
654
655# Follow logs in real time
656crush logs --follow
657```
658
659Want more logging? Run `crush` with the `--debug` flag, or enable it in the
660config:
661
662```json
663{
664 "$schema": "https://charm.land/crush.json",
665 "options": {
666 "debug": true,
667 "debug_lsp": true
668 }
669}
670```
671
672## Desktop Notifications
673
674Crush defaults to sending desktop notifications that let you know:
675
676- When its turn is finished (automatically cancelled when you interact with the
677 chat interface)
678- When it's waiting for permission to execute a tool (automatically cancelled
679 when you interact with the permission dialog)
680
681### Disabling notifications
682
683If you prefer to work without desktop notifications, you can disable them in
684your `crush.json` config.
685
686```json
687{
688 "$schema": "https://charm.land/crush.json",
689 "options": {
690 "disable_notifications": true
691 }
692}
693```
694
695## Provider Auto-Updates
696
697By default, Crush automatically checks for the latest and greatest list of
698providers and models from [Catwalk](https://github.com/charmbracelet/catwalk),
699the open source Crush provider database. This means that when new providers and
700models are available, or when model metadata changes, Crush automatically
701updates your local configuration.
702
703### Disabling automatic provider updates
704
705For those with restricted internet access, or those who prefer to work in
706air-gapped environments, this might not be want you want, and this feature can
707be disabled.
708
709To disable automatic provider updates, set `disable_provider_auto_update` into
710your `crush.json` config:
711
712```json
713{
714 "$schema": "https://charm.land/crush.json",
715 "options": {
716 "disable_provider_auto_update": true
717 }
718}
719```
720
721Or set the `CRUSH_DISABLE_PROVIDER_AUTO_UPDATE` environment variable:
722
723```bash
724export CRUSH_DISABLE_PROVIDER_AUTO_UPDATE=1
725```
726
727### Manually updating providers
728
729Manually updating providers is possible with the `crush update-providers`
730command:
731
732```bash
733# Update providers remotely from Catwalk.
734crush update-providers
735
736# Update providers from a custom Catwalk base URL.
737crush update-providers https://example.com/
738
739# Update providers from a local file.
740crush update-providers /path/to/local-providers.json
741
742# Reset providers to the embedded version, embedded at crush at build time.
743crush update-providers embedded
744
745# For more info:
746crush update-providers --help
747```
748
749## Metrics
750
751Crush records pseudonymous usage metrics (tied to a device-specific hash),
752which maintainers rely on to inform development and support priorities. The
753metrics include solely usage metadata; prompts and responses are NEVER
754collected.
755
756Details on exactly what’s collected are in the source code ([here](https://github.com/charmbracelet/crush/tree/main/internal/event)
757and [here](https://github.com/charmbracelet/crush/blob/main/internal/llm/agent/event.go)).
758
759You can opt out of metrics collection at any time by setting the environment
760variable by setting the following in your environment:
761
762```bash
763export CRUSH_DISABLE_METRICS=1
764```
765
766Or by setting the following in your config:
767
768```json
769{
770 "options": {
771 "disable_metrics": true
772 }
773}
774```
775
776Crush also respects the [`DO_NOT_TRACK`](https://consoledonottrack.com)
777convention which can be enabled via `export DO_NOT_TRACK=1`.
778
779## A Note on Claude Max and GitHub Copilot
780
781Crush only supports model providers through official, compliant APIs. We do not
782support or endorse any methods that rely on personal Claude Max and GitHub
783Copilot accounts or OAuth workarounds, which violate Anthropic and
784Microsoft’s Terms of Service.
785
786We’re committed to building sustainable, trusted integrations with model
787providers. If you’re a provider interested in working with us,
788[reach out](mailto:vt100@charm.sh).
789
790## Contributing
791
792See the [contributing guide](https://github.com/charmbracelet/crush?tab=contributing-ov-file#contributing).
793
794## Whatcha think?
795
796We’d love to hear your thoughts on this project. Need help? We gotchu. You can find us on:
797
798- [Twitter](https://twitter.com/charmcli)
799- [Slack](https://charm.land/slack)
800- [Discord][discord]
801- [The Fediverse](https://mastodon.social/@charmcli)
802- [Bluesky](https://bsky.app/profile/charm.land)
803
804[discord]: https://charm.land/discord
805
806## License
807
808[FSL-1.1-MIT](https://github.com/charmbracelet/crush/raw/main/LICENSE.md)
809
810---
811
812Part of [Charm](https://charm.land).
813
814<a href="https://charm.land/"><img alt="The Charm logo" width="400" src="https://stuff.charm.sh/charm-banner-next.jpg" /></a>
815
816<!--prettier-ignore-->
817Charm热爱开源 • Charm loves open source