A · leads
Agent-Reach
97.4
112,653 stars · MIT
Workflow Automation
Agent-Reach leads by 5.2 · narrow
A · leads
97.4
112,653 stars · MIT
B
92.2
30,757 stars · Apache-2.0
Agent-Reach versus gpt-researcher is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 97.4 for Agent-Reach and 92.2 for gpt-researcher.
Agent-Reach has 112,653 GitHub stars to gpt-researcher's 30,757, a gap of 81,896 (3.66×). Forks are 10,094 for Agent-Reach and 4,236 for gpt-researcher. On the log scale used inside this pair, adoption is 100 versus 89, and the fork community is 100 versus 91.
Push history: Agent-Reach was last pushed on 08 November 2026 (9 days ago), and gpt-researcher was last pushed on 12 November 2026 (5 days ago). Open issues stand at 133 for Agent-Reach (0.001 per star) and 56 for gpt-researcher (0.002 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. gpt-researcher 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 gpt-researcher. This is a procurement signal, not legal advice.
In Workflow Automation, both Agent-Reach (112,653 stars) and gpt-researcher (30,757 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, gpt-researcher 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 adoption at 11 points (100 vs 89), and the tightest is self-hosting at 0 points (100 vs 100).
Agent-Reach finishes ahead at 97.4 against gpt-researcher at 92.2, a 5.2 point narrow 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 | gpt-researcher |
|---|---|---|
| GitHub stars | 112,653 | 30,757 |
| Forks | 10,094 | 4,236 |
| Open issues | 133 | 56 |
| Adoption | 100 | 89 |
| Activity | 92 | 92 |
| Community | 100 | 91 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 92.2 |
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
An autonomous agent that conducts deep research on any data using any LLM providers
Agent-Reach has more GitHub stars: 112,653 versus 30,757 for gpt-researcher. The gap is 81,896 stars.
gpt-researcher was pushed more recently: 12 November 2026 versus 08 November 2026 for Agent-Reach. That is 4 days apart.
Yes. This catalog marks both Agent-Reach and gpt-researcher 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. gpt-researcher 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 gpt-researcher scores 92.2. This page calls that a narrow lead for Agent-Reach.