Use it when you can own the wrapper
Our CLI-Hub run installed successfully in 32 seconds, built in 3 seconds and finished pytest with 157 passed and 7 failed. Use CLI-Anything if you want reusable commands for an application and can inspect the wrapper and its output. Skip it if you need one generation pass to deliver complete, dependable control of a complex application: MangoFisher's Electron report describes few commands and low execution success.
CLI-Anything combines a catalog of existing command-line tools with an agent-driven generator for missing interfaces. A harness is the adapter code that gives an application named commands. CLI-Hub helps you find and install these tools; the generator asks a coding agent to create an adapter. The project's getting-started guide separates these two routes. Your decision starts with which route you actually need.
What people use CLI-Anything for
Creators report useful diagrams, office documents and rendered scenes, with a much narrower task in each case than controlling an entire application. These are attributed demonstrations, so you can judge the output the presenter describes rather than inherit a blanket claim about application coverage.
| Who used it | What they did | Reported outcome |
|---|---|---|
| Chase Hannegan, Chase AI | Asked Claude Code to use a generated draw.io CLI for a SaaS backend architecture diagram | A diagram with shading, layout and interconnected components |
| Presenter of “CLI-Anything: Turn ANY App into a CLI for Claude Code & Codex” | Asked an agent to find a diagramming tool through CLI-Hub | The agent selected draw.io, installed its CLI and exported a PNG |
| The same presenter | Created a Writer document, added a heading and table, then exported it | A PDF produced through headless LibreOffice |
| The same presenter | Created a Blender scene, added a cube and requested a Cycles render | Blender rendered the image in the background |
The discovery demonstration is the most interesting reason to start with the Hub. The presenter says the agent chose draw.io without being told which tool to use. That is a different purchase decision from wanting an agent to write integration code: you may get the task done with a tool somebody has already adapted.
The LibreOffice example also explains why “control the application” needs care. In issue #61, a user questioned why most commands worked without LibreOffice installed. The maintainer answered that the approach targets artifact formats rather than wrapping the application's compiled binary. Editing an intermediate document and calling the original program to render it can be useful. It doesn't mean every menu action has a corresponding command.
What happened when we ran it
Our November 2, 2026 run at commit 34f5195 installed CLI-Hub in 32 seconds and built it in 3 seconds, then the test command failed after 10 seconds with 157 passed and 7 failed. The tested project was ./cli-hub/. The seven failures all named analytics tests and reported a missing home directory.
There is also a newer, narrower attempt. On November 21, the quickstart-lib recipe used commit 34f519533bc1 and installed the PyPI CLI-Hub package in a fresh unprivileged container. It then reached a step designed to run a Python example. That step failed because the README has no Python code block to run. The documented entry point is a terminal command, so this stop describes a recipe mismatch rather than a failed diagram, render or document export. Teardown completed successfully.
The figures below belong to the November 2 source run. Keeping that scope explicit prevents a package installation from turning into a claim about a generated application's reliability.
| Check | Our recorded result | What you can take from it |
|---|---|---|
| Install | Succeeded in 32 seconds; 37 dependencies; 38 MB on disk | The recorded CLI-Hub dependency setup completed |
| Build | Succeeded in 3 seconds | The configured build step completed |
| Tests | Exit 1 after 10 seconds; 157 passed, 7 failed of 164 | The suite did not pass |
| Failure text | RuntimeError: Could not determine home directory. | Every named failure was in TestAnalytics |
| Dependency audit | pip-audit: 0 known vulnerabilities | The audit reported no known dependency vulnerabilities |
| Repository scan | 7 CI workflow files, a tests directory, no Dockerfile detected | Automation files exist; this is not a CI success result |
Installation and build completed before the run went wrong. Pytest then listed test_track_event_sends_request, the install and uninstall event-name cases, launch tracking, and the human, agent and detection-context visit cases. All seven ended with RuntimeError: Could not determine home directory. The pytest summary itself says 2.06 seconds; the enclosing test step took 10 seconds. Those are different scopes, not competing timings.
The configured sandbox had 3 CPUs and 8 GB RAM, with image label ghcr.io/astral-sh/uv:python3.12-bookworm. The label alone doesn't establish the runtime or operating-system version. The checkout scan counted 1,872 files, roughly 321,103 source lines and 63 MB. A developer changing CLI-Hub is working inside a much larger repository of adapters, rather than a standalone package of that checkout size.
Where people get stuck: successful commands can lose the work
Kdenlive user abcfy2 reported commands that announced a successful import while leaving the saved project unchanged in issue #214. That is a more consequential failure than an ugly help screen: an agent could proceed on the assumption that its previous action persisted.
| Report | What happened | Resolution shown in the thread |
|---|---|---|
| abcfy2, Kdenlive #214 | Non-interactive mutations left the project file unchanged; suggested save flags were absent | Maintainer supplied commit 18f75791f30bf7612fc1b0aae7e79c969e9db080; reporter replied “Great. It works.” |
| abcfy2, Kdenlive #213 | An exported native project failed to open correctly | Maintainer proposed commit 1b90df1b7f56f33365d9a8f2650096a0a3600e41; reporter's last reply still says it failed |
| howelljiang, gedit #16 | The generated program appeared mock-like and didn't interact with gedit | Reporter explored D-Bus; maintainer suggested refinement and adding IPC to the source; the discussion closed after an explanation |
| MangoFisher, Electron #154 | Generated commands covered little of a complex enterprise application and executed unreliably | Maintainer suggested stronger models, refinement and human supervision; no successful repair appears in the thread |
Read the two Kdenlive threads together. One has a clear reporter confirmation after a concrete fix. The other has a proposed fix followed by a failure report. A closed issue badge cannot substitute for that last exchange.
The gedit case changes what you should ask a generator to prove. D-Bus is a way for programs on a desktop to communicate; IPC means communication between processes. The proposed repair could involve changing gedit itself to expose that communication. If you chose this project to avoid writing application-specific integration code, that is a substantial change in the work you are accepting.
A terminal quickstart and an agent plugin are separate setup jobs
CLI-Hub's documented entry point is pip install cli-anything-hub, followed by space-separated cli-hub subcommands. The getting-started guide gives Python 3.10 or newer as a prerequisite and tells you to install the underlying application when a selected CLI needs it.
pip install cli-anything-hub
cli-hub list
cli-hub search image
cli-hub info gimp
cli-hub install gimp
cli-hub launch gimp
These are documentation examples, not extra commands from our measured run. Inspecting the entry before installation lets you see which tool you are choosing. Installing a wrapper doesn't supply Blender, GIMP or another rendering backend automatically just because the wrapper appears in a catalog.
For generation in Claude Code, the README describes adding the HKUDS marketplace and installing its plugin. In issue #19, MOKA-AI-Team-code reported that /cli-anything:cli-anything worked in Claude Code 2.x. HustLion described a manual-install workaround, while a later Windows 10 user still couldn't find the commands. The maintainer suggested WSL, a Linux environment on Windows, rather than recording a completed Windows fix.
Generation also needs the coding agent and model access you choose. The README warns that weaker models can produce incomplete or incorrect interfaces and that refinement may be needed. Account for that review work before treating the generator as a replacement for maintaining an adapter.
Security fixes concern the wrapper's real powers
The repository's news reports a GIMP Script-Fu path-injection fix and a change routing untrusted XML-family input through defusedxml. These are specific fixes to command and document handling, which matter because the wrappers read files and invoke real software.
For your first task, use copies of documents in a disposable working directory. Inspect the command's destination, the application's actual output and any service credentials involved. This is our operating recommendation: a structured command is easier to read than an agent clicking around a screen, but readability doesn't grant it permission to overwrite the only copy of your work.
The November 2 dependency audit reported zero known vulnerabilities. That result concerns the scanned dependencies; it isn't a security assessment of generated commands, every adapter, or the files and APIs you allow an agent to reach. The failing analytics test names also deserve their precise scope: they concern event tracking, without showing what network traffic an actual deployment sends.
Repeated work multiplies the importance of saved artifacts
The Kdenlive non-interactive report shows why checking persistence belongs before scheduling repeated work. A command can print an imported clip and still leave the on-disk project unchanged. For an unattended job, specify the output file and read it back before the next stage consumes it.
Our suggested acceptance check has two distinct parts. First, reopen the saved native project in the target application. Then render or export the deliverable you will actually hand over. A readable project and a correct exported file answer different questions, as the two Kdenlive reports demonstrate. Keep the original input alongside the output so a later refinement has a concrete regression example.
A commenter in the dev.to discussion asks about API safety and usage charges. For metered services, treat billing as a separate requirement from document undo. A local command's confirmation, dry-run option or state history should only earn trust for the operations its implementation actually guards.
CLI-Anything vs MCP servers, Computer Use and Playwright
A maintained integration that already covers your task is the first alternative to generating one. The presenter of “CLI-Anything: Claude Code Can Now Run ANY App” recommends an existing maintained MCP server when available. MCP, Model Context Protocol, is the interface AI assistants use to call external tools.
| Option | Choose it when | Basis for that choice |
|---|---|---|
| CLI-Anything | You want an existing application harness, or can own a new adapter | Hub distribution and the generator are separate documented paths |
| An existing maintained MCP server | Your target already has the operations you need | The video-1 presenter recommends using it before generating another integration |
| Claude Computer Use | You need GUI access and aren't choosing to build an application adapter | SkipCI's comparison frames this as the GUI-access versus adapter-work decision |
| Playwright MCP | Your task is in a web browser | Microsoft documents browser control through structured accessibility snapshots |
| Composio | Your task needs service connections with per-user authentication and sessions | Its SDK README documents per-user sessions, authentication and triggers |
The useful comparison is the work you need done, including authentication and the final artifact. A document renderer, a browser form and an authenticated SaaS action aren't interchangeable just because an agent can invoke each from a terminal.
CLI and MCP can also coexist. In issue #90, furkankoykiran describes a browser harness using DOMShell as its MCP backend, with filesystem-style page exploration and a daemon that keeps the connection alive. Choosing a command-line front end doesn't require removing a protocol that already works underneath it.
What the other reviews get wrong
MindStudio's guide prints hyphenated CLI-Hub command names, while HKUDS documents a cli-hub executable with separate subcommands. Copying the guide's cli-hub-install-<name> spelling would send you away from the documented cli-hub install <name> interface.
The cli-anything.dev introduction gives an npm package and a natural-language command as its quickstart. That is an identity mismatch for this review: its npm instructions are different from HKUDS's Python Hub and coding-agent plugin. Start at the HKUDS repository instead of trusting a matching product name in a search result.
Clianything.net promises full capabilities with zero compromises and displays a universal-sounding pass-rate claim. Its completeness language conflicts with what MangoFisher and howelljiang reported about Electron and gedit. Our own CLI-Hub suite also had seven failures. Historical harness results and a later Hub suite cover different things, so neither should be flattened into a universal guarantee.
The Chase AI FAQ says closed-source software can't work. The OpenAPI thread contains a later maintainer statement that specification-driven generation is supported through the standard flow. Source access still affects the generator's route, but an API specification is another input worth distinguishing from an opaque compiled binary.
Reddit user company_url_finder describes translating requests into clicks and field entry in r/BestGitHubRepos. The artifact-format explanation in issue #61 describes a different mechanism. On X, RoundtableSpace separates the Hub from the generator and reminds readers that the real application is still needed. That distinction is more useful than a promise to control almost any app.
Clianything.net also labels the project MIT and presents an older, smaller application list. The current HKUDS README states Apache License 2.0, and repository news records later additions such as QGIS and Calibre. A catalog count needs a date and a definition of what counts as an included tool.
Questions people ask
CLI-Anything gives agents command-line adapters for software, with CLI-Hub for finding existing tools and a generator for creating new ones. The getting-started guide explicitly offers both paths.
What is CLI-Anything, and how does it turn application functionality into commands?
A coding agent analyzes the target's source and builds a command-line harness. The maintainer's LibreOffice explanation says the approach targets artifact formats rather than wrapping compiled GUIs. That means document manipulation and invoking a renderer can be separate operations.
Where is the HKUDS/CLI-Anything GitHub repository?
The repository is github.com/HKUDS/CLI-Anything. Use that owner and repository name to distinguish the project from similarly named sites, forks and packages.
How do I use CLI-Anything Hub to install an existing CLI?
Install cli-anything-hub, browse with cli-hub list, inspect a tool with cli-hub info <name>, then use cli-hub install <name>. The guide also documents update, uninstall and launch commands. Install the underlying application when that tool needs it.
Does CLI-Anything support WPS, and what setup does it require?
A WPS installation route is an open question here, rather than a recommendation. WPS appears in autocomplete searches, which shows a query, not a working integration. The testing boundary below explains why we aren't giving you a guessed installation command.
How do I use CLI-Anything with Blender?
The video-4 presenter describes starting the Blender CLI's interactive prompt, creating a scene, adding a cube and rendering through Cycles. The reported render used Blender in the background. Choose the Blender harness and its prerequisites rather than expecting the Hub package alone to render a scene.
How do I install and use the CLI-Anything Zotero integration?
Start by inspecting Zotero's current Hub entry. Repository news says the Zotero CLI moved to a standalone repository and the Hub added remote skill-file support. Follow that entry's installation and skill documentation rather than assuming the old repository directory is the current distribution route.
How do I use CLI-Anything with Inkscape?
Use the Inkscape harness and inspect its command help for the operation you need. The video-4 walkthrough names Inkscape in the Hub catalog, and repository news records an Inkscape auto-save fix. Make saved SVG output part of your acceptance check.
Can CLI-Anything automate websites and browser interactions?
A browser harness exists in the project's development history. In issue #90, furkankoykiran reports PR #118 using DOMShell as an MCP backend, with navigation, page exploration, interaction commands and an interactive prompt. That is a concrete web route rather than proof that any website can be converted from its URL.
Does CLI-Anything support Android and Android TV applications?
A maintainer says codebases from any platform can be inputs, but androidteam2018 reports an Android TV attempt that produced simplistic, effectively unusable tests with Gemini 3 Pro. Issue #11 closes after discussion without showing a working replacement.
Do I need source code, or can CLI-Anything work with closed-source software?
An exposed API specification is another documented route: omerarslan0 says OpenAPI-to-CLI generation is supported through the standard flow. That statement isn't a promise to recover arbitrary capabilities from a binary without source or a usable API.
Why does Claude Code say 'Unknown skill: cli-anything', and which command works in version 2.x?
Some users in issue #19 report success with /cli-anything:cli-anything or a manual plugin installation. The later Windows report still lacked visible plugin commands, so the thread gives troubleshooting routes rather than one confirmed fix for every platform.
How can I generate more complete and accurate commands for a complex application?
The maintainer recommends refinement, stronger models and human supervision in MangoFisher's Electron thread. Treat those as suggested remedies. The thread contains no later successful run from MangoFisher that would turn the advice into a demonstrated repair.
What we have not tested yet
Our runs cover CLI-Hub setup and source checks, plus a quickstart recipe that stopped before a Python snippet. We have not tested a generated application workflow, reopened a native project, rendered a Blender scene or exported an office document ourselves. Creator demonstrations remain attributed demonstrations. The November 2 test tail identifies the home-directory error without assigning its cause to the sandbox, test design or application, and no fix was verified in that run.
We have no verified WPS installation path, command inventory or completed task. Zotero and Inkscape appear in project documentation, but our lab has not completed their workflows. Android TV success, a repaired enterprise Electron wrapper and Kdenlive native-project compatibility need task-level follow-up. The Kdenlive persistence repair has reporter confirmation; the separate native-project thread ends with another failure.
We have not measured concurrent work, sustained reliability, generation or refinement costs, or the advertised cost advantage over MCP. The video title's cheaper-than-MCP claim lacks a controlled comparison of complete tasks, including failed attempts. We also haven't tested whether dry-run, undo or confirmations prevent metered API charges, or inspected live telemetry and credentials handling. A website readiness score describes a website, not the reliability of an installed application wrapper.
For your next evaluation, choose one task whose result you can inspect in the original application. Keep the input, generated commands, saved native project and final export together. If that task fails, you will have an actionable integration bug rather than another encouraging terminal transcript.


