A
agent-desktop
90.9
24,948 stars · Apache-2.0
Workflow Automation
Agent-Reach leads by 6.5 · narrow
A
90.9
24,948 stars · Apache-2.0
B · leads
97.4
112,653 stars · MIT
agent-desktop versus Agent-Reach is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. agent-desktop is written mainly in Rust; Agent-Reach is written mainly in Python. The composite score is 90.9 for agent-desktop and 97.4 for Agent-Reach.
Agent-Reach has 112,653 GitHub stars to agent-desktop's 24,948, a gap of 87,705 (4.52×). Forks are 1,864 for agent-desktop and 10,094 for Agent-Reach. On the log scale used inside this pair, adoption is 87 versus 100, and the fork community is 82 versus 100.
Push history: agent-desktop was last pushed on 17 November 2026 (0 days ago), and Agent-Reach was last pushed on 08 November 2026 (9 days ago). Open issues stand at 260 for agent-desktop (0.010 per star) and 133 for Agent-Reach (0.001 per star). Issue-health scores are 84 and 96; activity scores are 100 and 92.
agent-desktop 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. 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. License scores in this pair are 96 for agent-desktop and 96 for Agent-Reach. This is a procurement signal, not legal advice.
In Workflow Automation, both agent-desktop (24,948 stars) and Agent-Reach (112,653 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-desktop is open source, Agent-Reach is open source.
The lead is split. agent-desktop is furthest ahead on recent activity (100 to 92), while Agent-Reach is furthest ahead on fork community (100 to 82). Choose the dimension a rollout cannot compromise on.
Agent-Reach finishes ahead at 97.4 against agent-desktop at 90.9, a 6.5 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-desktop | Agent-Reach |
|---|---|---|
| GitHub stars | 24,948 | 112,653 |
| Forks | 1,864 | 10,094 |
| Open issues | 260 | 133 |
| Adoption | 87 | 100 |
| Activity | 100 | 92 |
| Community | 82 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.9 | 97.4 |
Computer use CLI for AI agents
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Agent-Reach has more GitHub stars: 112,653 versus 24,948 for agent-desktop. The gap is 87,705 stars.
agent-desktop 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-desktop and Agent-Reach as self-hostable. Confirm each project's deploy docs before you plan a migration.
agent-desktop 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Agent-Reach scores 97.4 and agent-desktop scores 90.9. This page calls that a narrow lead for Agent-Reach.