Skip to content
DevUtils Online

Workflow Automation

Agent-Reach vs paperclip

Agent-Reach leads by 1.7 · narrow

Agent-Reach versus paperclip 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; paperclip is written mainly in TypeScript. The composite score is 96.4 for Agent-Reach and 94.7 for paperclip.

paperclip has 114,484 GitHub stars to Agent-Reach's 112,653, a gap of 1,831 (1.02×). Forks are 10,094 for Agent-Reach and 18,987 for paperclip. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 94 versus 100.

Push history: Agent-Reach was last pushed on 08 November 2026 (9 days ago), and paperclip was last pushed on 17 November 2026 (0 days ago). Open issues stand at 133 for Agent-Reach (0.001 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 96 and 52; activity scores are 92 and 100.

Both Agent-Reach and paperclip 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 paperclip (114,484 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, paperclip is open source.

The lead is split. Agent-Reach is furthest ahead on issue health (96 to 52), while paperclip is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.

Agent-Reach finishes ahead at 96.4 against paperclip at 94.7, a 1.7 point narrow 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.

Agent-Reach versus paperclip metrics
Signal Agent-Reach paperclip
GitHub stars 112,653 114,484
Forks 10,094 18,987
Open issues 133 6,806
Adoption 100 100
Activity 92 100
Community 94 100
Issue health 96 52
License 96 96
Self-hosting 100 100
Composite 96.4 94.7

Agent-Reach

Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, Agent-Reach or paperclip?

paperclip has more GitHub stars: 114,484 versus 112,653 for Agent-Reach. The gap is 1,831 stars.

Which was updated more recently, Agent-Reach or paperclip?

paperclip was pushed more recently: 17 November 2026 versus 08 November 2026 for Agent-Reach. That is 9 days apart.

Can I self-host both Agent-Reach and paperclip?

Yes. This catalog marks both Agent-Reach and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, Agent-Reach or paperclip?

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. paperclip 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 Agent-Reach vs paperclip score?

Agent-Reach scores 96.4 and paperclip scores 94.7. This page calls that a narrow lead for Agent-Reach.

Related comparisons