[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f106wkas209flc":3},{"code":4,"message":5,"data":6,"timestamp":41},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":31,"summary_md":32,"topic":33,"github_topics":36,"license":37,"homepage":38,"updated_at":39,"history":40},"HKUDS\u002FCLI-Anything",9,"\"CLI-Anything: Making ALL Software Agent-Native\" -- CLI-Hub:https:\u002F\u002Fclianything.cc\u002F","Python",56813,5092,6906,230,[16,22,28],{"id":17,"title":18,"points":19,"comments":20,"posted_at":21},47360545,"CLI-Anything",4,0,"2026-03-13",{"id":23,"title":24,"points":25,"comments":26,"posted_at":27},47734871,"Show HN: I benchmarked MCP vs. CLI for browser automation. MCP wins by 25x",2,1,"2026-04-11",{"id":29,"title":30,"points":25,"comments":26,"posted_at":21},47364480,"Turn any software into an agent-native CLI","Generated command-line harnesses that let AI agents drive desktop apps that only have a GUI.","## The problem\nAgents are good at shell tools and bad at everything else. Most real software -- CAD, video editors, DAWs, GIS, note apps -- exposes no stable programmatic interface, so an agent that can write code still cannot open Blender and produce a render. CLI-Anything's answer is a registry of per-application CLI harnesses plus a hub (`cli-hub install \u003Cname>`) that puts a scriptable, JSON-friendly surface in front of each app, so the agent calls commands instead of clicking.\n\n## What's different\nMCP servers are the usual way to give an agent access to an app, and they work, but each server is bespoke, often stateful, and hard to test from a terminal. CLI-Anything standardizes on the CLI as the agent interface: subcommands, JSON plus human output, and a packaged `SKILL.md` describing usage. That is a narrower, more inspectable contract than a general-purpose MCP tool surface, and it composes with the existing skills ecosystems (`npx skills add ...`). The trade-off is that every app still needs someone to write and maintain a harness, and behaviour depends on how well the underlying app can be scripted (headless modes, local REST APIs, vendor CLIs).\n\n## Who it's for\nTeams running coding agents (Claude Code, Cursor and similar) who want those agents to touch creative and productivity tools, not just repositories. Also useful for people who prefer driving an app from a shell with reproducible, testable commands. Look elsewhere if you need a single deeply integrated plugin for one app, or if your workflow is pure text\u002Fcode -- the harness layer adds nothing there.\n\n## Cost of adoption\nPython >=3.10, Apache-2.0, installed via pip for the hub. Per-harness requirements vary a lot: some wrap a local app on macOS or Windows, some need vendor credentials or tokens, some need the target app installed. Maturity is uneven by harness -- the README's news feed shows a constant stream of merges, security hardening (token handling, `defusedxml` for untrusted input) and E2E test additions, which is a good sign but also means quality differs between entries. Expect to read the individual harness docs and verify against your app version.\n\n## Verdict\nThis is a young project by age (created 2026-03-08) but not by attention: roughly 56.8k stars and +3,303 in a single week, ranked #14 on the weekly board. That pattern says a large community formed fast around the registry model, not that every harness is polished. The idea -- CLI as the agent-native interface -- is practical and low-magic, and the test\u002Fsecurity discipline visible in recent PRs is more than most hype projects show. Worth adopting for a specific app whose harness is well tested; not worth adopting wholesale as infrastructure without checking the harness you need.",{"slug":34,"name":35},"ai-engineering","AI Engineering",[],"Apache-2.0","https:\u002F\u002Fclianything.cc\u002F","2026-10-24T15:35:25Z",[],1792868587]