A
Agent-S
85.0
12,994 stars · Apache-2.0
AI Agents
ECC leads by 14.1 · clear
A
85.0
12,994 stars · Apache-2.0
B · leads
99.1
305,069 stars · MIT
Agent-S versus ECC is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Agent-S is written mainly in Python; ECC is written mainly in JavaScript. The composite score is 85.0 for Agent-S and 99.1 for ECC.
ECC has 305,069 GitHub stars to Agent-S's 12,994, a gap of 292,075 (23.48×). Forks are 1,519 for Agent-S and 44,923 for ECC. On the log scale used inside this pair, adoption is 75 versus 100, and the fork community is 68 versus 100.
Push history: Agent-S was last pushed on 13 November 2026 (3 days ago), and ECC was last pushed on 17 November 2026 (0 days ago). Open issues stand at 82 for Agent-S (0.006 per star) and 149 for ECC (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
Agent-S 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. 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. License scores in this pair are 96 for Agent-S and 96 for ECC. This is a procurement signal, not legal advice.
In AI Agents, both Agent-S (12,994 stars) and ECC (305,069 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: Agent-S is open source, ECC 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 32 points (68 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
ECC finishes ahead at 99.1 against Agent-S at 85.0, a 14.1 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | Agent-S | ECC |
|---|---|---|
| GitHub stars | 12,994 | 305,069 |
| Forks | 1,519 | 44,923 |
| Open issues | 82 | 149 |
| Adoption | 75 | 100 |
| Activity | 100 | 100 |
| Community | 68 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 85.0 | 99.1 |
Agent S: the state-of-the-art open source computer use agents
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
ECC has more GitHub stars: 305,069 versus 12,994 for Agent-S. The gap is 292,075 stars.
ECC was pushed more recently: 17 November 2026 versus 13 November 2026 for Agent-S. That is 3 days apart.
Yes. This catalog marks both Agent-S and ECC as self-hostable. Confirm each project's deploy docs before you plan a migration.
Agent-S 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
ECC scores 99.1 and Agent-S scores 85.0. This page calls that a clear lead for ECC.