Skip to content
DevUtils Online

AI Agents

ECC vs gemini-cli

ECC leads by 5.4 · narrow

A · leads

ECC

99.1

305,069 stars · MIT

ECC versus gemini-cli is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. ECC is written mainly in JavaScript; gemini-cli is written mainly in TypeScript. The composite score is 99.1 for ECC and 93.7 for gemini-cli.

ECC has 305,069 GitHub stars to gemini-cli's 108,897, a gap of 196,172 (2.80×). Forks are 44,923 for ECC and 14,956 for gemini-cli. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 90.

Push history: ECC was last pushed on 17 November 2026 (0 days ago), and gemini-cli was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for ECC (0.000 per star) and 739 for gemini-cli (0.007 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.

ECC is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. gemini-cli is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for ECC and 96 for gemini-cli. This is a procurement signal, not legal advice.

In AI Agents, both ECC (305,069 stars) and gemini-cli (108,897 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: ECC is open source, gemini-cli is open source.

ECC is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 12 points (96 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).

ECC finishes ahead at 99.1 against gemini-cli at 93.7, a 5.4 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

ECC versus gemini-cli metrics
Signal ECC gemini-cli
GitHub stars 305,069 108,897
Forks 44,923 14,956
Open issues 149 739
Adoption 100 92
Activity 100 100
Community 100 90
Issue health 96 84
License 96 96
Self-hosting 100 100
Composite 99.1 93.7

ECC

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, ECC or gemini-cli?

ECC has more GitHub stars: 305,069 versus 108,897 for gemini-cli. The gap is 196,172 stars.

Which was updated more recently, ECC or gemini-cli?

Both were last pushed on 17 November 2026.

Can I self-host both ECC and gemini-cli?

Yes. This catalog marks both ECC and gemini-cli as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, ECC or gemini-cli?

ECC is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. gemini-cli is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the ECC vs gemini-cli score?

ECC scores 99.1 and gemini-cli scores 93.7. This page calls that a narrow lead for ECC.

Related comparisons