CruxCLI vs OpenCode
CruxCLI is a hard fork of OpenCode that adds an intelligence layer on top of the same client/server architecture. Both are open source, provider-agnostic terminal AI coding agents with 75+ provider support, LSP integration, and plugin APIs. CruxCLI adds 24 task-specific modes with model tier mapping, per-mode token budgets, workspace checkpoints, and CruxDev convergence engine integration. OpenCode has a vastly larger community (129,357 stars, 800+ contributors) and GitLab Agent Platform integration.
Feature comparison
| Feature | CruxCLI | OpenCode |
|---|---|---|
| Open source (MIT) | ✓ | ✓ |
| Provider-agnostic (75+) | ✓ | ✓ |
| Client/server architecture | ✓ | ✓ |
| LSP integration (30+ servers) | ✓ | ✓ |
| Plugin API | ✓ | ✓ |
| Custom modes | ✓ | ✓ |
| VS Code extension | ✓ | ✓ |
| Desktop app | ✓ | ✓ |
| Mode → model tier mapping | ✓ | ✗ |
| Token budget system | ✓ | ✗ |
| Workspace checkpoints | ✓ | ✗ |
| Convergence engine | ✓ | ✗ |
| Correction detection | ✓ | ✗ |
| GitLab Agent Platform | ✗ | ✓ |
| Free model tier (Zen) | ✗ | ✓ |
| Node.js runtime support | ✗ | ✓ |
| GitHub stars | New | 129k |
| Contributors | Solo | 800+ |
Where CruxCLI wins
Intelligence layer
CruxCLI's 24 task-specific modes each map to a model tier (strong, balanced, fast). A code review uses Opus; a format task uses Haiku. OpenCode sends every task to whatever model you last selected, regardless of complexity.
Token budgets
Per-mode token budgets with 75% warning and 90% hard stop. OpenCode uses step-count limits — 10 tool calls could be 500 tokens or 50,000. Token budgets measure actual cost.
Workspace checkpoints
Automatic git-based snapshots before every destructive operation. Up to 50 per project. OpenCode has no checkpoint system.
CruxDev convergence
Autonomous audit-fix loops that run until two consecutive clean passes. OpenCode has no convergence methodology — the user decides when code is done.
Where OpenCode wins
Community
129,357 stars, 800+ contributors, 5M+ monthly developers. OpenCode has the largest community of any open-source terminal AI agent. CruxCLI is new with no established community yet. This is the biggest gap.
GitLab integration
OpenCode v1.3.0 added GitLab Agent Platform integration. CruxCLI does not have GitLab-specific integration yet.
Free model tier
OpenCode offers a free "Zen" tier. CruxCLI requires users to bring their own API keys.
Release cadence
Near-daily releases (737+) with a large contributor base. CruxCLI has a smaller, focused release schedule.
Frequently asked questions
What is the difference between CruxCLI and OpenCode?
CruxCLI is a hard fork of OpenCode that adds an intelligence layer: 24 task-specific modes with model tier mapping, per-mode token budgets, workspace checkpoints, correction detection, and CruxDev convergence engine integration. OpenCode has a larger community (129k stars) and GitLab integration.
Is CruxCLI compatible with OpenCode configurations?
CruxCLI forked from OpenCode and shares the same client/server architecture, LSP integration, and plugin API. Configuration files use a similar format (cruxcli.jsonc vs opencode.json) but are not directly compatible due to the added mode and token budget settings.
Should I use CruxCLI or OpenCode?
Use CruxCLI if you want mode-based model selection, token budgets, workspace checkpoints, and convergence-driven workflows. Use OpenCode if you need the largest community ecosystem, GitLab Agent Platform integration, or Node.js runtime support.
Try CruxCLI
Same architecture as OpenCode, plus intelligence. One command to install.