cua

trycua/cua

Scale computer-use 2.0 with open-source drivers, cross-OS fleets, and benchmarks for training, evaluation, and data generation.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 12, 2026
today
Ship score
100/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 25,941 → 28,246 (Sep 22 – Oct 6, 2026)
History starts 2026-09-22, the first weekly sample after this repo joined the directory.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
29.4K
Forks
2.1K
Open issues
1.2K
Watchers
94
Primary language
Rust
Created
Jan 31, 2025
Owner
trycua · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 43 startups in the directory ship primarily in Rust.

Topics

#agent#ai-agent#apple#computer-use#computer-use-agent#containerization#cua#desktop-automation#hacktoberfest#lume#macos#manus#operator#swift#virtualization#virtualization-framework#windows#windows-sandbox

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 95%, self-hostable 49%, hosted offering 48%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 2026-09-22, found by the weekly discovery job at confidence 0.93. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-12This is the badge for trycua/cua, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/trycua/cua.svg)](https://ossean.com/trycua/cua)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.