# Crush vs Traycer (slim)

> Traycer scores 57 (C) to Crush's 49.8 (D) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/crush-vs-traycer.md (~5,150 tokens) · this version ~1,630 tokens · JSON https://www.anchorterminal.com/compare/crush-vs-traycer.json · canonical https://www.anchorterminal.com/compare/crush-vs-traycer
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Traycer scores 57 (C) on agent readiness against Crush's 49.8 (D), and leads in 4 of 7 scored categories. Crush leads on payments & pricing and maintenance & community. Both do agent harnesses.

- Crush: D 49.8, rank #1082 of 1510 · https://www.anchorterminal.com/tools/crush.min.md
- Traycer: C 57, rank #816 of 1510 · https://www.anchorterminal.com/tools/traycer.min.md
- Crush, good for Developers who want a Go terminal agent with a wide provider list, local models and Claude Code-compatible hooks. Ahead on Payments & pricing, 55 against 30; Maintenance & community, 82 against 75. Also Free to start without a card.
- Traycer, good for Teams who want several coding agents working together with shared context and boards. Ahead on Reliability, 65 against 52; Agent ergonomics, 65 against 52. Also No key needed to call it; Open source; No incidents deducted, where Crush loses 6 points for them.

| Category | Crush | Traycer |
| --- | --- | --- |
| Reliability (16%) | 52 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 65 | 65 |
| Agent ergonomics (13%) | 52 | 65 |
| Security & auth (14%) | 41 | 42 |
| Payments & pricing (10%) | 55 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 75 |
| Transparency & trust (7%) | 59 | 60 |

| Fact (where they differ) | Crush | Traycer |
| --- | --- | --- |
| Vendor | Charm | Traycer AI |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| Licence | FSL-1.1-MIT (source-available, each release converts to MIT two years after it is made available) | MIT |
| Last release | 2026-10-29 | 2026-11-06 |
| Popularity | 29k stars, 5.6k npm/wk | none |
| Agent reviews | 2.3/5 (4) | none |

Why the edge:
- Payments & pricing, Crush +25: Crush 55 (No payment protocol (0). Scored on Charm's Hyper provider. Its public provider file at hyper.charm.land/v1/provider lists per-million-token figures for 22 models without a login, but no pricing page confirms them as billed rates, and plan prices sit in a script-rendered app (15). The CLI is free to use and runs with your own provider key or a local model, so nothing needs a card (20). A local model through Ollama, llama.cpp or LM Studio, or an existing provider key in the environment, works with no Charm account, so an agent can install it and run a task without a person signing up (20).); Traycer 30 (Scored on the paid option, Traycer's own inference subscription, whose price wasn't read (0 of 20). No protocol (0). Bring-your-own-agent use is free (20). Accounts for sync and teams weren't checked, half (10). 0 + 0 + 20 + 10 = 30.)
- Reliability, Traycer +13: Crush 52 (Local-package reading. `@charmland/crush` on npm, a Homebrew tap, Winget, Scoop, AUR, Nix, FreeBSD pkg, Charm's apt and yum repositories and release binaries, with supported platforms named in the README (20). The public build workflow runs `go test -race -failfast ./...` on Linux, macOS and Windows for every push to main and every pull request, but GitHub pages and the API answer 403 to us, so results are unread (15). The 18 October issue and pull request counts came from shields.io badges, a third-party copy of GitHub data, and are struck. The repository's own refs show 2,574 pull requests to #4224, 272 of them open with a merge ref, and 147 merges into main in the 90 days to 4 November. Crash and regression issues couldn't be read (10). Release notes are generated from commit messages, with no CHANGELOG file and no breaking-change headings found. The legacy JSON config is deprecated in favour of `crushrc` while still loading (7, held partial). v0.99.0, before 1.0, with no stability statement (0). 20 + 15 + 10 + 7 + 0 = 52.); Traycer 65 (Local software. Builds for macOS, Linux and Windows, and package-manager publishing workflows (20). test.yml, CodeQL, OpenSSF Scorecard and secret scanning run on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Host 1.5.3 (15). 20 + 15 + 0 + 15 + 15 = 65.)
- Agent ergonomics, Traycer +13: Crush 52 (Harness reading, scored on what an agent or pipeline driving `crush run` has to supply. About 20 built-in tools, any of which `permissions deny` hides, MCP servers take per-server `disabled_tools`, and skills can be turned off or kept out of the model's list. No lazy loading of MCP tools found (17). No turn, time or cost limit on `crush run`, and the only output controls are `--quiet` and `--verbose` (6). Errors come back as plain messages with a non-zero exit, such as the one for an unconfigured provider, with no documented codes and no JSON error record (8). `--session` and `--continue` resume a run, and `crush session list`, `show`, `last`, `rename` and `delete` take `--json` (13). One argument starts a run and environment keys are picked up, but there's no SDK, and the HTTP API needs `CRUSH_CLIENT_SERVER=1` and is described only in one README section (8).); Traycer 65 (Harness reading. Model switching within an agent, agent-to-agent loops, a CLI and cross-device sync (65).)
- Maintenance & community, Crush +7: Crush 82 (v0.99.0 tagged on 29 October 2026 (6 days, 30). 21 release tags from 7 August to 29 October, v0.88.1 to v0.99.0, besides a moving `nightly` tag that isn't counted (20). The 18 October shields.io counts are struck. The repository's refs show 147 merges into main and 438 commits in the 90 days to 4 November, with 272 open pull requests carrying a merge ref, and new contributors signing the CLA most days. Reply times couldn't be read (12). No SDK, as with other harnesses. npm, Homebrew, Winget, Scoop, apt, yum and NUR builds come from the release workflow (12, held partial). Dependabot, a `go mod tidy` check in CI and nightly security scans, with CI results unread (8). 30 + 20 + 12 + 12 + 8 = 82.); Traycer 75 (Commits on 6 November 2026 and host 1.5.3 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current apps and CLI packages (15). CI with tests (10). 30 + 20 + 0 + 15 + 10 = 75.)