Crush
Terminal-native coding agent from Charm with multi-model support, LSP context, MCP connectivity, and strong Windows/macOS/Linux support.
Do not bounce yet
Read the fit check, compare one alternative, then decide whether the vendor page is still your best next click.
Quick Verdict
Fast fit check before you leave the page
Make the fit call first. Vendor pages are good at selling, but they rarely tell you where the product is a bad match.
- Developers who prefer terminal-native coding workflows over AI-heavy IDE experiences
- Teams comparing serious Claude Code alternatives with better provider optionality
- Advanced users who want MCP servers, LSP context, and repo-local configuration in one CLI tool
- FSL-1.1-MIT is source-available rather than plain open source today, which matters for teams with strict OSS-only procurement rules
- You still need to bring your own provider credentials or subscriptions, so the software may be free while real usage is not
- Fast-moving products can shift config, supported providers, and workflow details quickly during adoption
Compare Next
Take one more internal step before the vendor pitch
This is where visitors usually jump out too early. Read one deeper take or open one alternative so the next click is informed instead of impulsive.
Alternative profile
Aider
Open-source terminal coding agent with git-native edits, repo mapping, and broad model support
Alternative profile
Claude Code
Agentic AI coding assistant that lives in your terminal, understands your entire codebase and automates routine tasks
Alternative profile
Claude Code Chat
Beautiful chat interface for Claude Code right inside VS Code, no terminal required
Crush is Charm's answer to the terminal coding agent category: a polished CLI experience with serious model-provider flexibility, LSP-enhanced context, MCP extensibility, and project-level configuration instead of a thin chat shell around bash. It belongs in the same shortlist as Claude Code and OpenCode, but the licensing nuance matters because Crush is source-available under FSL-1.1-MIT rather than plain open source today.
Crush is Charm’s terminal-first coding agent for developers who want serious agentic coding workflows without being locked to one model vendor or one editor. It supports multiple providers, lets you switch models mid-session, pulls in extra context through LSPs, connects to MCP servers over stdio/http/sse, and gives teams fine-grained control over permissions, config, and project-specific behavior. The catch is licensing: Crush is public code under FSL-1.1-MIT rather than plain OSI open source today, so it deserves a more precise label than the repo currently had.
Why Choose Crush?
Crush stands out because Charm understands terminal product design better than most teams shipping agent tools into the shell.
Provider flexibility gives teams leverage: the best model, cheapest model, and easiest-to-buy model are rarely the same thing for long.
LSP plus MCP makes Crush more extensible and context-aware than many newer coding agents that stop at shell commands and file edits.
If you want a modern terminal-native agent without committing your whole workflow to a single editor vendor, Crush is an obvious tool to evaluate.
Key Features
Terminal-first coding agent from Charm with a polished TUI instead of an editor plugin pretending to be a workflow
Multi-provider model support with the ability to switch providers and models mid-session while preserving context
LSP integration for stronger repo awareness and developer-like context gathering inside the terminal flow
MCP support across stdio, HTTP, and SSE for extending the agent with external tools and services
Project-local and global JSON configuration for permissions, provider settings, ignore rules, notifications, and behavior tuning
Cross-platform support across macOS, Linux, and Windows including PowerShell-friendly install paths
Pros & Cons
- Charm knows terminal UX, and it shows: Crush feels like a real developer tool, not a hacked-on shell wrapper
- Provider flexibility matters because coding model quality, pricing, and availability change too fast to standardize on one vendor forever
- LSP plus MCP gives advanced users a credible path to deeper context and richer toolchains without abandoning the CLI
- The public repo, fast release cadence, and 20k+ star traction make it much easier to trust than most newly launched coding agents
- FSL-1.1-MIT is source-available rather than plain open source today, which matters for teams with strict OSS-only procurement rules
- You still need to bring your own provider credentials or subscriptions, so the software may be free while real usage is not
- Fast-moving products can shift config, supported providers, and workflow details quickly during adoption
- Permission controls are powerful, but teams still need to think carefully before normalizing yolo-style execution habits
Detailed Use Cases for Crush
Crush fits developers who live in shells, tmux, and git-heavy workflows and do not want an IDE to become the mandatory control plane for agentic coding.
Teams can route Crush through different commercial or compatible APIs over time instead of tying their coding workflow to one vendor roadmap.
Crush can connect to MCP servers over stdio, HTTP, or SSE, which gives advanced users a path to richer integrations than basic shell-only agents.
LSP configuration, ignore files, permissions, and project-local settings help Crush adapt to real repositories rather than acting like a stateless demo assistant.
Who Should Use Crush?
Developers who prefer terminal-native coding workflows over AI-heavy IDE experiences
Teams comparing serious Claude Code alternatives with better provider optionality
Advanced users who want MCP servers, LSP context, and repo-local configuration in one CLI tool
Builders who care about inspectable codebases but also need honest licensing distinctions
Perfect For
Terminal-native pair programming and implementation work for developers who prefer shell-first workflows
Model-provider experimentation when teams want to compare Claude, OpenAI, Gemini, Groq, local models, or custom compatible APIs
Project-specific agent setup using local crush.json files, ignore rules, and permissions tuned to a repo
Advanced CLI workflows that benefit from LSP context, MCP extensions, and reusable agent skills
Technical Details
Crush Comparisons & Alternatives
Crush vs Claude Code
Crush vs OpenCode
Charm Crush review
terminal coding agent with MCP
source available AI coding tool
Developers compare Crush with other vibe coding tools when they need a better workflow fit, not just a better landing page.
Direct Competitors
Claude Code
OpenCode
Aider
Goose
Similar Tools You Might Like
Open-source terminal session manager for running and supervising multiple AI coding agents across isolated git worktrees.
Open-source terminal and web session manager for running multiple AI coding agents across isolated git worktrees and sandboxes.
Open-source terminal coding agent with git-native edits, repo mapping, and broad model support
Alternative Tools to Consider
Open-source terminal coding agent with git-native edits, repo mapping, and broad model support
Agentic AI coding assistant that lives in your terminal, understands your entire codebase and automates routine tasks
Beautiful chat interface for Claude Code right inside VS Code, no terminal required
Open-source terminal dashboard for tracking Claude Code token usage, burn rate, and predicted session cutoffs.
Open-source local AI agent from Block with CLI and desktop workflows, MCP extensibility, and real engineering task automation.
Open-source coding agent for the terminal with provider-agnostic model support, built-in agents, and optional desktop/IDE surfaces.
Do one more comparison before you commit to Crush
Strong picks usually survive one more internal check. Read deeper, compare a neighbor, then leave for the vendor page if the fit still holds.