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