CLI-Anything (HKUDS)Partly tested🇨🇳 CN

HKUDS's CLI-Anything wraps software such as Blender in command-line tools, so Claude Code / Cursor / OpenClaw can install them from CLI-Hub with one command instead of clicking through screenshots

HKUDS open-sourced CLI-Anything (Apache-2.0, ~57k★, clianything.cc): make software agent-ready with stable CLIs instead of screenshot clicking. CLI-Hub (`pip install cli-anything-hub`) browses/installs community harnesses for Blender, GIMP, LibreOffice and more; a generator skill runs a 7-phase HARNESS pipeline when the registry has no match. Works with Claude Code, Cursor, Pi, OpenClaw and peers. @MirrortekUK's Chinese post framed it as dropping pixel-click automation. On our test machine we installed cli-anything-hub in a venv and ran `cli-hub list` / `search blender` / `info blender`; we did not install Blender itself or run a full `/cli-anything` generation pipeline.

Visit site CLI-Anything (HKUDS) ↗
Pricing
Free
Region
Global
Where it's from
Chinese community
Added
Oct 26, 2026
Tested on
Oct 26, 2026
Version we used
cli-anything-hub (PyPI install 2026-10-26); upstream HKUDS/CLI-Anything ~57k★
Categories
Automation & AgentsCoding
Original author
HKUDS / CLI-Anything ↗
Our test
Partly tested
Cost / time
The repo and hub client are free (Apache-2.0). You still install upstream apps (Blender, GIMP, …) under their own licenses, and you need your Claude / Cursor (etc.) plan for the agent side.
Source
X @MirrortekUK(中文介绍) ↗GitHub HKUDS/CLI-Anything ↗CLI-Hub ↗clianything.cc ↗

The task

Let coding / desktop agents operate Blender, GIMP, office suites and similar apps via CLIs instead of screenshot clicking, reusing community harnesses from a public registry.

Steps

  1. Install the hub: `pip install cli-anything-hub` (prefer a venv).
  2. Browse: `cli-hub list`, `cli-hub search image`, `cli-hub info blender`.
  3. Install a harness: `cli-hub install blender` (or gimp, etc.); you still need the upstream app locally (e.g. Blender ≥4.2).
  4. Run: `cli-hub launch blender …`. Optionally give agents the meta-skill: `npx skills add HKUDS/CLI-Anything --skill cli-hub-meta-skill -g -y`, then ask them to find a CLI-Hub tool for the task.
  5. If nothing fits: install the CLI-Anything plugin for Claude Code / Pi / OpenCode, run `/cli-anything ./gimp` (or a repo URL) through the 7-phase HARNESS, then `/cli-anything:refine` to extend it.
  6. Chinese docs: README_CN.md; new CLIs go through upstream CONTRIBUTING / wishlist issues.

Prompt

Find an appropriate CLI in CLI-Hub and use it to background-render a Blender scene—no screenshot clicking.

What the author says

The project claims to make "any software" agent-native: CLI-Hub one-command installs for community harnesses, plus a 7-phase HARNESS generator for new CLIs; demos cover CAD, 3D, subtitles, games and more. README badges advertise a large passing test suite. @MirrortekUK highlights natural-language use, one-command community installs, and multi-agent support.

Our test

Installed cli-anything-hub in a test venv and successfully ran `cli-hub list` (categories such as 3D/AI/AUDIO with blender, gimp, comfyui, …), `cli-hub search blender`, and `cli-hub info blender` (Requires blender ≥4.2, Status: not installed). We did not install Blender, run `cli-hub install`, or execute the `/cli-anything` 7-phase generator. Stars ~57,108 as of 2026-10-26.

What we found when we tried it:The hub client installs and the registry is searchable; info matches the README. Driving Blender (etc.) for real and generating a new harness were not verified here.

How to get in

GitHub, CLI-Hub and the Chinese README are public; the intro post is on X (login may be required). pip/npm installs have no geo wall; some upstream apps have their own OS requirements.

Who it suits

People who want agents on pro desktop apps and are done with flaky screenshot clicking; also a pattern for wrapping internal tools in a CLI first.

Pitfalls

  • cli-hub installs the harness, not the upstream app; Blender / GIMP / etc. must be installed separately at compatible versions (e.g. blender ≥4.2).
  • Not every GUI action has a stable CLI; generator quality varies—run the repo's required tests before trusting a new harness.
  • Some harnesses touch local files or remote APIs (Zoom, clouds); tighten secrets per each CLI's docs.
  • The news feed moves fast—trust current README / skill text over old screenshots.
  • "Make all software agent-native" is a direction, not a warranty: complex UI may still need refine or a human.

More in this category