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` | Amazon Bedrock (Claude) |
254| `AWS_SECRET_ACCESS_KEY` | Amazon Bedrock (Claude) |
255| `AWS_REGION` | Amazon Bedrock (Claude) |
256| `AWS_PROFILE` | Amazon Bedrock (Custom Profile) |
257| `AWS_BEARER_TOKEN_BEDROCK` | Amazon 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### Desktop notifications
428
429Crush sends desktop notifications when a tool call requires permission and when
430the agent finishes its turn. They're only sent when the terminal window isn't
431focused _and_ your terminal supports reporting the focus state.
432
433```json
434{
435 "$schema": "https://charm.land/crush.json",
436 "options": {
437 "disable_notifications": true // default
438 }
439}
440```
441
442To disable desktop notifications, set `disable_notifications` to `true` in your
443configuration. On macOS, notifications currently lack icons due to platform
444limitations.
445
446### Initialization
447
448When you initialize a project, Crush analyzes your codebase and creates
449a context file that helps it work more effectively in future sessions.
450By default, this file is named `AGENTS.md`, but you can customize the
451name and location with the `initialize_as` option:
452
453```json
454{
455 "$schema": "https://charm.land/crush.json",
456 "options": {
457 "initialize_as": "AGENTS.md"
458 }
459}
460```
461
462This is useful if you prefer a different naming convention or want to
463place the file in a specific directory (e.g., `CRUSH.md` or
464`docs/LLMs.md`). Crush will fill the file with project-specific context
465like build commands, code patterns, and conventions it discovered during
466initialization.
467
468### Attribution Settings
469
470By default, Crush adds attribution information to Git commits and pull requests
471it creates. You can customize this behavior with the `attribution` option:
472
473```json
474{
475 "$schema": "https://charm.land/crush.json",
476 "options": {
477 "attribution": {
478 "trailer_style": "co-authored-by",
479 "generated_with": true
480 }
481 }
482}
483```
484
485- `trailer_style`: Controls the attribution trailer added to commit messages
486 (default: `assisted-by`)
487 - `assisted-by`: Adds `Assisted-by: [Model Name] via Crush <crush@charm.land>`
488 (includes the model name)
489 - `co-authored-by`: Adds `Co-Authored-By: Crush <crush@charm.land>`
490 - `none`: No attribution trailer
491- `generated_with`: When true (default), adds `💘 Generated with Crush` line to
492 commit messages and PR descriptions
493
494### Custom Providers
495
496Crush supports custom provider configurations for both OpenAI-compatible and
497Anthropic-compatible APIs.
498
499> [!NOTE]
500> Note that we support two "types" for OpenAI. Make sure to choose the right one
501> to ensure the best experience!
502> * `openai` should be used when proxying or routing requests through OpenAI.
503> * `openai-compat` should be used when using non-OpenAI providers that have OpenAI-compatible APIs.
504
505#### OpenAI-Compatible APIs
506
507Here’s an example configuration for Deepseek, which uses an OpenAI-compatible
508API. Don't forget to set `DEEPSEEK_API_KEY` in your environment.
509
510```json
511{
512 "$schema": "https://charm.land/crush.json",
513 "providers": {
514 "deepseek": {
515 "type": "openai-compat",
516 "base_url": "https://api.deepseek.com/v1",
517 "api_key": "$DEEPSEEK_API_KEY",
518 "models": [
519 {
520 "id": "deepseek-chat",
521 "name": "Deepseek V3",
522 "cost_per_1m_in": 0.27,
523 "cost_per_1m_out": 1.1,
524 "cost_per_1m_in_cached": 0.07,
525 "cost_per_1m_out_cached": 1.1,
526 "context_window": 64000,
527 "default_max_tokens": 5000
528 }
529 ]
530 }
531 }
532}
533```
534
535#### Anthropic-Compatible APIs
536
537Custom Anthropic-compatible providers follow this format:
538
539```json
540{
541 "$schema": "https://charm.land/crush.json",
542 "providers": {
543 "custom-anthropic": {
544 "type": "anthropic",
545 "base_url": "https://api.anthropic.com/v1",
546 "api_key": "$ANTHROPIC_API_KEY",
547 "extra_headers": {
548 "anthropic-version": "2023-06-01"
549 },
550 "models": [
551 {
552 "id": "claude-sonnet-4-20250514",
553 "name": "Claude Sonnet 4",
554 "cost_per_1m_in": 3,
555 "cost_per_1m_out": 15,
556 "cost_per_1m_in_cached": 3.75,
557 "cost_per_1m_out_cached": 0.3,
558 "context_window": 200000,
559 "default_max_tokens": 50000,
560 "can_reason": true,
561 "supports_attachments": true
562 }
563 ]
564 }
565 }
566}
567```
568
569### Amazon Bedrock
570
571Crush currently supports running Anthropic models through Bedrock, with caching disabled.
572
573- A Bedrock provider will appear once you have AWS configured, i.e. `aws configure`
574- Crush also expects the `AWS_REGION` or `AWS_DEFAULT_REGION` to be set
575- To use a specific AWS profile set `AWS_PROFILE` in your environment, i.e. `AWS_PROFILE=myprofile crush`
576- Alternatively to `aws configure`, you can also just set `AWS_BEARER_TOKEN_BEDROCK`
577
578### Vertex AI Platform
579
580Vertex AI will appear in the list of available providers when `VERTEXAI_PROJECT` and `VERTEXAI_LOCATION` are set. You will also need to be authenticated:
581
582```bash
583gcloud auth application-default login
584```
585
586To add specific models to the configuration, configure as such:
587
588```json
589{
590 "$schema": "https://charm.land/crush.json",
591 "providers": {
592 "vertexai": {
593 "models": [
594 {
595 "id": "claude-sonnet-4@20250514",
596 "name": "VertexAI Sonnet 4",
597 "cost_per_1m_in": 3,
598 "cost_per_1m_out": 15,
599 "cost_per_1m_in_cached": 3.75,
600 "cost_per_1m_out_cached": 0.3,
601 "context_window": 200000,
602 "default_max_tokens": 50000,
603 "can_reason": true,
604 "supports_attachments": true
605 }
606 ]
607 }
608 }
609}
610```
611
612### Local Models
613
614Local models can also be configured via OpenAI-compatible API. Here are two common examples:
615
616#### Ollama
617
618```json
619{
620 "providers": {
621 "ollama": {
622 "name": "Ollama",
623 "base_url": "http://localhost:11434/v1/",
624 "type": "openai-compat",
625 "models": [
626 {
627 "name": "Qwen 3 30B",
628 "id": "qwen3:30b",
629 "context_window": 256000,
630 "default_max_tokens": 20000
631 }
632 ]
633 }
634 }
635}
636```
637
638#### LM Studio
639
640```json
641{
642 "providers": {
643 "lmstudio": {
644 "name": "LM Studio",
645 "base_url": "http://localhost:1234/v1/",
646 "type": "openai-compat",
647 "models": [
648 {
649 "name": "Qwen 3 30B",
650 "id": "qwen/qwen3-30b-a3b-2507",
651 "context_window": 256000,
652 "default_max_tokens": 20000
653 }
654 ]
655 }
656 }
657}
658```
659
660## Logging
661
662Sometimes you need to look at logs. Luckily, Crush logs all sorts of
663stuff. Logs are stored in `./.crush/logs/crush.log` relative to the project.
664
665The CLI also contains some helper commands to make perusing recent logs easier:
666
667```bash
668# Print the last 1000 lines
669crush logs
670
671# Print the last 500 lines
672crush logs --tail 500
673
674# Follow logs in real time
675crush logs --follow
676```
677
678Want more logging? Run `crush` with the `--debug` flag, or enable it in the
679config:
680
681```json
682{
683 "$schema": "https://charm.land/crush.json",
684 "options": {
685 "debug": true,
686 "debug_lsp": true
687 }
688}
689```
690
691## Provider Auto-Updates
692
693By default, Crush automatically checks for the latest and greatest list of
694providers and models from [Catwalk](https://github.com/charmbracelet/catwalk),
695the open source Crush provider database. This means that when new providers and
696models are available, or when model metadata changes, Crush automatically
697updates your local configuration.
698
699### Disabling automatic provider updates
700
701For those with restricted internet access, or those who prefer to work in
702air-gapped environments, this might not be want you want, and this feature can
703be disabled.
704
705To disable automatic provider updates, set `disable_provider_auto_update` into
706your `crush.json` config:
707
708```json
709{
710 "$schema": "https://charm.land/crush.json",
711 "options": {
712 "disable_provider_auto_update": true
713 }
714}
715```
716
717Or set the `CRUSH_DISABLE_PROVIDER_AUTO_UPDATE` environment variable:
718
719```bash
720export CRUSH_DISABLE_PROVIDER_AUTO_UPDATE=1
721```
722
723### Manually updating providers
724
725Manually updating providers is possible with the `crush update-providers`
726command:
727
728```bash
729# Update providers remotely from Catwalk.
730crush update-providers
731
732# Update providers from a custom Catwalk base URL.
733crush update-providers https://example.com/
734
735# Update providers from a local file.
736crush update-providers /path/to/local-providers.json
737
738# Reset providers to the embedded version, embedded at crush at build time.
739crush update-providers embedded
740
741# For more info:
742crush update-providers --help
743```
744
745## Metrics
746
747Crush records pseudonymous usage metrics (tied to a device-specific hash),
748which maintainers rely on to inform development and support priorities. The
749metrics include solely usage metadata; prompts and responses are NEVER
750collected.
751
752Details on exactly what’s collected are in the source code ([here](https://github.com/charmbracelet/crush/tree/main/internal/event)
753and [here](https://github.com/charmbracelet/crush/blob/main/internal/llm/agent/event.go)).
754
755You can opt out of metrics collection at any time by setting the environment
756variable by setting the following in your environment:
757
758```bash
759export CRUSH_DISABLE_METRICS=1
760```
761
762Or by setting the following in your config:
763
764```json
765{
766 "options": {
767 "disable_metrics": true
768 }
769}
770```
771
772Crush also respects the [`DO_NOT_TRACK`](https://consoledonottrack.com)
773convention which can be enabled via `export DO_NOT_TRACK=1`.
774
775## A Note on Claude Max and GitHub Copilot
776
777Crush only supports model providers through official, compliant APIs. We do not
778support or endorse any methods that rely on personal Claude Max and GitHub
779Copilot accounts or OAuth workarounds, which violate Anthropic and
780Microsoft’s Terms of Service.
781
782We’re committed to building sustainable, trusted integrations with model
783providers. If you’re a provider interested in working with us,
784[reach out](mailto:vt100@charm.sh).
785
786## Contributing
787
788See the [contributing guide](https://github.com/charmbracelet/crush?tab=contributing-ov-file#contributing).
789
790## Whatcha think?
791
792We’d love to hear your thoughts on this project. Need help? We gotchu. You can find us on:
793
794- [Twitter](https://twitter.com/charmcli)
795- [Slack](https://charm.land/slack)
796- [Discord][discord]
797- [The Fediverse](https://mastodon.social/@charmcli)
798- [Bluesky](https://bsky.app/profile/charm.land)
799
800[discord]: https://charm.land/discord
801
802## License
803
804[FSL-1.1-MIT](https://github.com/charmbracelet/crush/raw/main/LICENSE.md)
805
806---
807
808Part of [Charm](https://charm.land).
809
810<a href="https://charm.land/"><img alt="The Charm logo" width="400" src="https://stuff.charm.sh/charm-banner-next.jpg" /></a>
811
812<!--prettier-ignore-->
813Charm热爱开源 • Charm loves open source