All directories
AgentEngineeringProduct

Crush

charmbracelet/crush

Agentic coding for everyone — approachable agentic coding UX from Charmbracelet. GitHub: charmbracelet/crush (~27k stars).

00

GitHub repository

https://github.com/charmbracelet/crush
01

Overview

Crush (charmbracelet/crush) is listed in LimeDock Directories as an AI agent resource. Agentic coding for everyone — approachable agentic coding UX from Charmbracelet. Group: coding-agents. Community size: ~27k GitHub stars. Repo (copy/paste): https://github.com/charmbracelet/crush This page is a plain-English guide so searches for the GitHub project can land on how teams actually use it.

SaaSOther

Work with LimeDock

Using this skill? LimeDock can wire it into a durable automation you own.

Agents are a starting point. LimeDock turns the workflow into production automation your SaaS team owns — not another prompt library.

We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.

02

Link

https://github.com/charmbracelet/crush
03

Installation guide

Open the GitHub repository, then follow the README for your stack.

Official GitHub repository: https://github.com/charmbracelet/crush GitHub path: charmbracelet/crush

How to open it: 1. Copy: https://github.com/charmbracelet/crush 2. Clone or follow the README for your OS/stack. 3. Start with the smallest example before production use.

04

How to use it

**Simple example** You want an approachable agentic coding tool with great terminal UX.

1. Install Crush per the repo. 2. Run it on a sample project. 3. Complete one small feature with review.

05

Example prompts

  • Install Crush and walk through a first session.
  • Crush vs Aider for beginners?
  • How do we teach juniors to review agent diffs?
06

Use cases and examples

  • Evaluate charmbracelet/crush as an AI agent building block
  • Pilot Crush on one staging workflow
  • Compare against agents you already pay for
  • Document a team playbook after the pilot
07

Prerequisites

  • Terminal comfort
  • Model access
08

Tips

  • UX helps adoption — process still needs review.
  • Keep tasks small.