A · leads
agent-desktop
97.6
24,948 stars · Apache-2.0
Workflow Automation
agent-desktop leads by 5.2 · narrow
A · leads
97.6
24,948 stars · Apache-2.0
B
92.4
23,434 stars · AGPL-3.0
agent-desktop versus skyvern 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; skyvern is written mainly in Python. The composite score is 97.6 for agent-desktop and 92.4 for skyvern.
agent-desktop has 24,948 GitHub stars to skyvern's 23,434, a gap of 1,514 (1.06×). Forks are 1,864 for agent-desktop and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 98 versus 100.
Push history: agent-desktop was last pushed on 17 November 2026 (0 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 260 for agent-desktop (0.010 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for agent-desktop and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both agent-desktop (24,948 stars) and skyvern (23,434 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, skyvern is open source.
The lead is split. agent-desktop is furthest ahead on license flexibility (96 to 52), while skyvern is furthest ahead on fork community (100 to 98). Choose the dimension a rollout cannot compromise on.
agent-desktop finishes ahead at 97.6 against skyvern at 92.4, 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-desktop | skyvern |
|---|---|---|
| GitHub stars | 24,948 | 23,434 |
| Forks | 1,864 | 2,246 |
| Open issues | 260 | 301 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 98 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.6 | 92.4 |
Computer use CLI for AI agents
Automate browser based workflows with AI
agent-desktop has more GitHub stars: 24,948 versus 23,434 for skyvern. The gap is 1,514 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both agent-desktop and skyvern 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
agent-desktop scores 97.6 and skyvern scores 92.4. This page calls that a narrow lead for agent-desktop.