A · leads
Agent-Reach
97.4
112,653 stars · MIT
Workflow Automation
Agent-Reach leads by 7.7 · clear
A · leads
97.4
112,653 stars · MIT
B
89.7
11,796 stars · MIT
Agent-Reach versus loop-engineering is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Agent-Reach is written mainly in Python; loop-engineering is written mainly in TypeScript. The composite score is 97.4 for Agent-Reach and 89.7 for loop-engineering.
Agent-Reach has 112,653 GitHub stars to loop-engineering's 11,796, a gap of 100,857 (9.55×). Forks are 10,094 for Agent-Reach and 1,583 for loop-engineering. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 80.
Push history: Agent-Reach was last pushed on 08 November 2026 (9 days ago), and loop-engineering was last pushed on 17 November 2026 (0 days ago). Open issues stand at 133 for Agent-Reach (0.001 per star) and 23 for loop-engineering (0.002 per star). Issue-health scores are 96 and 96; activity scores are 92 and 100.
Both Agent-Reach and loop-engineering 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 Workflow Automation, both Agent-Reach (112,653 stars) and loop-engineering (11,796 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-Reach is open source, loop-engineering is open source.
The lead is split. Agent-Reach is furthest ahead on fork community (100 to 80), while loop-engineering is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
Agent-Reach finishes ahead at 97.4 against loop-engineering at 89.7, a 7.7 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-Reach | loop-engineering |
|---|---|---|
| GitHub stars | 112,653 | 11,796 |
| Forks | 10,094 | 1,583 |
| Open issues | 133 | 23 |
| Adoption | 100 | 81 |
| Activity | 92 | 100 |
| Community | 100 | 80 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 89.7 |
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Practical patterns, starters & CLI tools for loop engineering with AI coding agents. Design systems that prompt and orchestrate agents (inspired by Addy Osmani and Boris Cherny). Includes loop-audit, loop-init, loop-cost.
Agent-Reach has more GitHub stars: 112,653 versus 11,796 for loop-engineering. The gap is 100,857 stars.
loop-engineering was pushed more recently: 17 November 2026 versus 08 November 2026 for Agent-Reach. That is 9 days apart.
Yes. This catalog marks both Agent-Reach and loop-engineering as self-hostable. Confirm each project's deploy docs before you plan a migration.
Agent-Reach 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. loop-engineering 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.
Agent-Reach scores 97.4 and loop-engineering scores 89.7. This page calls that a clear lead for Agent-Reach.