Skip to content
DevUtils Online

AI Agents

ECC vs happy

ECC leads by 13.3 · clear

A · leads

ECC

99.1

305,069 stars · MIT

B

happy

85.8

24,678 stars · MIT

ECC versus happy 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; happy is written mainly in Swift. The composite score is 99.1 for ECC and 85.8 for happy.

ECC has 305,069 GitHub stars to happy's 24,678, a gap of 280,391 (12.36×). Forks are 44,923 for ECC and 2,123 for happy. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 72.

Push history: ECC was last pushed on 17 November 2026 (0 days ago), and happy was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for ECC (0.000 per star) and 1,111 for happy (0.045 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.

Both ECC and happy are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In AI Agents, both ECC (305,069 stars) and happy (24,678 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, happy 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 fork community at 28 points (100 vs 72), and the tightest is self-hosting at 0 points (100 vs 100).

ECC finishes ahead at 99.1 against happy at 85.8, a 13.3 point clear 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 happy metrics
Signal ECC happy
GitHub stars 305,069 24,678
Forks 44,923 2,123
Open issues 149 1,111
Adoption 100 80
Activity 100 100
Community 100 72
Issue health 96 70
License 96 96
Self-hosting 100 100
Composite 99.1 85.8

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

happy

Orchestrate Claude, Codex and Grok in one app. Open-source (MIT), reuses the subscriptions you already pay for.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, ECC or happy?

ECC has more GitHub stars: 305,069 versus 24,678 for happy. The gap is 280,391 stars.

Which was updated more recently, ECC or happy?

Both were last pushed on 17 November 2026.

Can I self-host both ECC and happy?

Yes. This catalog marks both ECC and happy 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 happy?

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. happy 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the ECC vs happy score?

ECC scores 99.1 and happy scores 85.8. This page calls that a clear lead for ECC.

Related comparisons