Gemini CLI, Crush, and Chrome DevTools MCP keep getting compared. They do three different jobs.

查看原文

ClaudeOpenAIGemini模型发布开源代码

gemini

热度趋势

趋势数据积累中

百分比基于当前可用热度信号，而非评论数或独立用户人数。

推荐理由

Claude 相关模型动态已经出现，适合跟踪能力变化、生态影响和后续可用性。

AI 摘要

Charm的TUI编码代理Crush，尽管用途不同，却常被拿来与Gemini CLI和Chrome DevTools MCP比较。Crush允许用户在会话中途切换AI模型，提供LSP增强的上下文，并支持Anthropic、OpenAI和Gemini等多种提供商。它以FSL-1.1-MIT协议开源，默认开启指标收集，但并非完全自主的SWE代理。其配置正从JSON过渡到crushrc。

I've been writing short, opinionated notes on coding-agent tools (stackgems.com — agent-curated, human veto, no sponsors). Three that landed in the catalog today are useful together because people treat them as interchangeable.

They're not.

Gemini CLI is Google's Apache 2.0 terminal agent: Gemini models, 1M context, search grounding, MCP, headless JSON, a GitHub Action for PR review. The catch isn't quality, it's lock-in. It is Gemini-bound, and since June Google has been pushing consumer users toward Antigravity CLI (agy). The OSS repo is still there; I would not bet a workflow on the old "sign in with Google, 1k requests/day" path.

https://stackgems.com/gems/gemini-cli

https://github.com/google-gemini/gemini-cli

Crush is Charm's TUI coding agent (Glow / Bubble Tea people). Switch models mid-session without losing context, LSP-enhanced context, MCP over http/stdio/sse, Agent Skills. Bring Anthropic, OpenAI, Gemini, OpenRouter, Ollama, Bedrock, or Charm Hyper. FSL-1.1-MIT is source-available, not Apache/MIT today (MIT after 2 years). Pre-1.0, config moving from JSON to crushrc. Not a fully autonomous SWE agent. Metrics on by default (DO_NOT_TRACK / CRUSH_DISABLE_METRICS).

https://stackgems.com/gems/crush

https://github.com/charmbracelet/crush

Chrome DevTools MCP is not a coding agent. Official Chrome DevTools team MCP server, so Cursor / Claude / Copilot get performance traces, network inspection, source-mapped console, screenshots, and Puppeteer that waits. Needs Node ≥ 22.12 (Node 20 fails). --autoConnect to a running Chrome. This is the DevTools surface; Playwright MCP (already in the catalog) is still the automation one. --slim for basic browsing. Chrome and Chrome for Testing only. Don't point it at a logged-in bank tab. Usage stats on by default (--no-usage-statistics to opt out).

https://stackgems.com/gems/chrome-devtools-mcp

https://github.com/ChromeDevTools/chrome-devtools-mcp

If you're assembling a stack: Crush (or Claude Code / Codex) for the agent, Chrome DevTools MCP for the browser, Gemini CLI only if you're already in Google's world and okay with the Antigravity migration.

Happy to take disagreements, especially if your Gemini CLI Google-login quota is still actually working.