HKUDS / CLI-ANYTHING
CLI-HUB
Making all software agent-native

Today's software
serves humans.
Tomorrow's users
will be agents.

CLI-Anything writes command line harnesses for software that never shipped one, so an agent can drive it the same way it drives anything else. The bridge is the CLI, and CLI-Hub is where the community-built ones live.

Most software assumes a person with a mouse. An agent has neither, so the gap is not intelligence. It is an interface that takes text and returns text.

pip install cli-anything-hub cli-hub install <name> github.com/HKUDS/CLI-Anything
The bridgeFour hops
+-----------+ | AGENT | has no mouse, reads and writes text +-----------+ | v +-----------+ | CLI | the layer this project generates +-----------+ | v +-----------+ | SOFTWARE | was written for a person +-----------+ | v +-----------+ | ARTIFACT | a file you can open and diff +-----------+
Installpip install cli-anything-hub
Add onecli-hub install <name>
Contributeopen a PR, the hub updates instantly
Software built for a person
The agent stalls at the GUI
agent > open the CAD file and extrude the base 4mm no command surface found falling back to screen control click (612, 344) toolbar moved after update click (598, 351) wrong panel retry 3 of 3 FAILED no artifact produced

Pixel driving breaks the moment a layout changes, and nothing about the failure is reusable by the next agent.

Same software, with a harness
The agent runs a command
agent > open the CAD file and extrude the base 4mm $ cad-cli open part.step $ cad-cli select face --name base $ cad-cli extrude --distance 4mm $ cad-cli preview --out preview.png OK artifact written: part_v2.step OK preview loop: 1 pass

Commands are inspectable, repeatable, and diffable. The README describes preview, live preview, and trajectory loops feeding real artifacts.

Artifacts the demos produce
> CAD builds
Parametric models driven from a command instead of a toolbar.
> 3D scenes
Scene assembly an agent can re-run after a review comment.
> Diagrams
Generated from text, so the diff is readable.
> Gameplay
Interactive software reached through a text surface.
> Subtitles
Media work that used to need a timeline UI.
> Your own harness
Open a PR and the hub updates instantly.

These six are the artifact types the README lists for its demos. Terminal transcripts above are illustrative.

The claim

Agent-native, not agent-adapted

Wrapping a GUI in vision is adaptation. Generating a command surface changes what the software is to a caller.

The hub

One install path

cli-hub install means a harness someone else wrote is a dependency rather than a fork of their setup.

The loop

Preview closes it

A command that renders a preview lets the agent check its own work, which is what makes the next call better than a guess.