A · leads
Agent-Reach
97.4
112,653 stars · MIT
Workflow Automation
Agent-Reach leads by 10.4 · clear
A · leads
97.4
112,653 stars · MIT
B
87.0
10,907 stars · Apache-2.0
Agent-Reach versus robotgo 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; robotgo is written mainly in Go. The composite score is 97.4 for Agent-Reach and 87.0 for robotgo.
Agent-Reach has 112,653 GitHub stars to robotgo's 10,907, a gap of 101,746 (10.33×). Forks are 10,094 for Agent-Reach and 968 for robotgo. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 75.
Push history: Agent-Reach was last pushed on 08 November 2026 (9 days ago), and robotgo was last pushed on 13 November 2026 (4 days ago). Open issues stand at 133 for Agent-Reach (0.001 per star) and 4 for robotgo (0.000 per star). Issue-health scores are 96 and 96; activity scores are 92 and 92.
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. robotgo 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 Agent-Reach and 96 for robotgo. This is a procurement signal, not legal advice.
In Workflow Automation, both Agent-Reach (112,653 stars) and robotgo (10,907 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, robotgo is open source.
Agent-Reach is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 25 points (100 vs 75), and the tightest is self-hosting at 0 points (100 vs 100).
Agent-Reach finishes ahead at 97.4 against robotgo at 87.0, a 10.4 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 | robotgo |
|---|---|---|
| GitHub stars | 112,653 | 10,907 |
| Forks | 10,094 | 968 |
| Open issues | 133 | 4 |
| Adoption | 100 | 80 |
| Activity | 92 | 92 |
| Community | 100 | 75 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 87.0 |
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
RobotGo, Go Native cross-platform RPA, GUI automation, Auto test and Computer use @vcaesar
Agent-Reach has more GitHub stars: 112,653 versus 10,907 for robotgo. The gap is 101,746 stars.
robotgo was pushed more recently: 13 November 2026 versus 08 November 2026 for Agent-Reach. That is 5 days apart.
Yes. This catalog marks both Agent-Reach and robotgo 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. robotgo 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.
Agent-Reach scores 97.4 and robotgo scores 87.0. This page calls that a clear lead for Agent-Reach.