A · leads
agent-desktop
96.1
24,948 stars · Apache-2.0
Workflow Automation
agent-desktop leads by 1.3 · narrow
A · leads
96.1
24,948 stars · Apache-2.0
B
94.8
27,230 stars · MIT
agent-desktop versus vagrant 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; vagrant is written mainly in Ruby. The composite score is 96.1 for agent-desktop and 94.8 for vagrant.
vagrant has 27,230 GitHub stars to agent-desktop's 24,948, a gap of 2,282 (1.09×). Forks are 1,864 for agent-desktop and 4,491 for vagrant. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 90 versus 100.
Push history: agent-desktop was last pushed on 17 November 2026 (0 days ago), and vagrant was last pushed on 12 November 2026 (5 days ago). Open issues stand at 260 for agent-desktop (0.010 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 84 and 70; 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. vagrant 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 vagrant. This is a procurement signal, not legal advice.
In Workflow Automation, both agent-desktop (24,948 stars) and vagrant (27,230 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, vagrant is open source.
The lead is split. agent-desktop is furthest ahead on issue health (84 to 70), while vagrant is furthest ahead on fork community (100 to 90). Choose the dimension a rollout cannot compromise on.
agent-desktop finishes ahead at 96.1 against vagrant at 94.8, a 1.3 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 | vagrant |
|---|---|---|
| GitHub stars | 24,948 | 27,230 |
| Forks | 1,864 | 4,491 |
| Open issues | 260 | 760 |
| Adoption | 99 | 100 |
| Activity | 100 | 92 |
| Community | 90 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.1 | 94.8 |
Computer use CLI for AI agents
Vagrant is a tool for building and distributing development environments.
vagrant has more GitHub stars: 27,230 versus 24,948 for agent-desktop. The gap is 2,282 stars.
agent-desktop was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.
Yes. This catalog marks both agent-desktop and vagrant 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. vagrant 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-desktop scores 96.1 and vagrant scores 94.8. This page calls that a narrow lead for agent-desktop.