Audited 2026-10-18 · Sources: GitHub repo + README, changelog, CLI-Hub registry docs. Tabletop audit — nothing installed.
The card
| Repo | HKUDS/CLI-Anything |
| Stars | 54.7k (GitHub API, audit date) |
| License | Apache-2.0 |
| Born | March 2026 · from HKUDS (HKU Data Science lab — academic origin) |
| What it is | "Making ALL software agent-native" — a community registry of agent-callable CLI harnesses for real programs (Blender, FreeCAD, ArcGIS, Obsidian, Zoom...), plus a package manager (CLI-Hub) to install them |
| Install surface | pip install cli-anything-hub then cli-hub install <name>; harnesses also installable via npx skills add |
What problem it solves
Agents think in tools. Most software on your machine isn't a tool — it's a GUI. CLI-Anything wraps real programs in agent-callable interfaces, so an agent can actually operate Blender or your GIS suite instead of describing how it would. It's the missing plumbing between "agent can reason" and "agent can drive your stack."
Our gate findings
| Gate | Finding |
|---|---|
| Upstream identity | Verified — HKUDS academic lab, Apache-2.0, public contribution pipeline (PRs per harness) |
| Security history | The changelog is the tell. March-May 2026 entries show real hardening: Sketch CLI token-file path-traversal fixed, Zoom token permissions tightened, installer guards against empty intros. A project that logs its security fixes in public is a project that takes them. |
| Registry risk | Community-submitted harnesses = community-submitted trust. Each wrapper is code an agent will run against a real app. The public registry structure helps (PRs are reviewable), but a harness is only as vetted as its review was. |
| Blast radius | By design it's everything the wrapped tool can do. A Blender CLI can run Blender scripts; a Zoom CLI can act in Zoom. Same rule as any agent-power tool: scope the workspace, then hand over the keys. |
Verdict: CAUTION. Serious engineering, academic provenance, visible security maintenance — and a purpose that makes it as powerful as whatever it wraps. Install specific harnesses you need, not the registry wholesale.
Best for
Power users who want agents operating desktop tools that were never built for automation — CAD, video editors, niche industry software. If your stack is already API-first, you don't need it.