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### Ignoring Files
331
332Crush respects `.gitignore` files by default, but you can also create a
333`.crushignore` file to specify additional files and directories that Crush
334should ignore. This is useful for excluding files that you want in version
335control but don't want Crush to consider when providing context.
336
337The `.crushignore` file uses the same syntax as `.gitignore` and can be placed
338in the root of your project or in subdirectories.
339
340### Allowing Tools
341
342By default, Crush will ask you for permission before running tool calls. If
343you'd like, you can allow tools to be executed without prompting you for
344permissions. Use this with care.
345
346```json
347{
348 "$schema": "https://charm.land/crush.json",
349 "permissions": {
350 "allowed_tools": [
351 "view",
352 "ls",
353 "grep",
354 "edit",
355 "mcp_context7_get-library-doc"
356 ]
357 }
358}
359```
360
361You can also skip all permission prompts entirely by running Crush with the
362`--yolo` flag. Be very, very careful with this feature.
363
364### Disabling Built-In Tools
365
366If you'd like to prevent Crush from using certain built-in tools entirely, you
367can disable them via the `options.disabled_tools` list. Disabled tools are
368completely hidden from the agent.
369
370```json
371{
372 "$schema": "https://charm.land/crush.json",
373 "options": {
374 "disabled_tools": [
375 "bash",
376 "sourcegraph"
377 ]
378 }
379}
380```
381
382To disable tools from MCP servers, see the [MCP config section](#mcps).
383
384### Agent Skills
385
386Crush supports the [Agent Skills](https://agentskills.io) open standard for
387extending agent capabilities with reusable skill packages. Skills are folders
388containing a `SKILL.md` file with instructions that Crush can discover and
389activate on demand.
390
391Skills are discovered from:
392
393- `~/.config/crush/skills/` on Unix (default, can be overridden with `CRUSH_SKILLS_DIR`)
394- `%LOCALAPPDATA%\crush\skills\` on Windows (default, can be overridden with `CRUSH_SKILLS_DIR`)
395- Additional paths configured via `options.skills_paths`
396
397```jsonc
398{
399 "$schema": "https://charm.land/crush.json",
400 "options": {
401 "skills_paths": [
402 "~/.config/crush/skills", // Windows: "%LOCALAPPDATA%\\crush\\skills",
403 "./project-skills"
404 ]
405 }
406}
407```
408
409You can get started with example skills from [anthropics/skills](https://github.com/anthropics/skills):
410
411```bash
412# Unix
413mkdir -p ~/.config/crush/skills
414cd ~/.config/crush/skills
415git clone https://github.com/anthropics/skills.git _temp
416mv _temp/skills/* . && rm -rf _temp
417```
418
419```powershell
420# Windows (PowerShell)
421mkdir -Force "$env:LOCALAPPDATA\crush\skills"
422cd "$env:LOCALAPPDATA\crush\skills"
423git clone https://github.com/anthropics/skills.git _temp
424mv _temp/skills/* . ; rm -r -force _temp
425```
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```jsonc
434{
435 "$schema": "https://charm.land/crush.json",
436 "options": {
437 "disable_notifications": false // 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` convention which can be enabled via
773`export DO_NOT_TRACK=1`.
774
775## Contributing
776
777See the [contributing guide](https://github.com/charmbracelet/crush?tab=contributing-ov-file#contributing).
778
779## Whatcha think?
780
781We’d love to hear your thoughts on this project. Need help? We gotchu. You can find us on:
782
783- [Twitter](https://twitter.com/charmcli)
784- [Slack](https://charm.land/slack)
785- [Discord][discord]
786- [The Fediverse](https://mastodon.social/@charmcli)
787- [Bluesky](https://bsky.app/profile/charm.land)
788
789[discord]: https://charm.land/discord
790
791## License
792
793[FSL-1.1-MIT](https://github.com/charmbracelet/crush/raw/main/LICENSE.md)
794
795---
796
797Part of [Charm](https://charm.land).
798
799<a href="https://charm.land/"><img alt="The Charm logo" width="400" src="https://stuff.charm.sh/charm-banner-next.jpg" /></a>
800
801<!--prettier-ignore-->
802Charm热爱开源 • Charm loves open source