A toolbelt for
your agents.

useclis is a directory of command-line tools that agents can use through a terminal. Find a CLI for the task, inspect its repository, and follow its documentation to get started.

What belongs here

The directory includes 115 CLIs across 11 categories. Some are designed specifically for agents, like browser automation tools and coding-agent runtimes. Others are established command-line tools for search, JSON, Git, deployments, and documents that fit shell-based agent workflows.

Each listing names an actual command-line entry point, explains a concrete use case, and links to the source repository and documentation. Examples are starting points; setup, authentication, and local context depend on the tool. Inclusion is not a certification of compatibility with every agent.

Agent workflow labels

The supplied 100-CLI source list marks 16 entries as “Documented” for agent/AI workflow support and leaves 84 as “Not marked in source list.” Listings preserve those labels. “Not marked” means the source list made no claim; it does not mean a CLI lacks agent support. Entries outside that list have no source-list label.

Go straight to the repository

Star counts, detected licenses, and commit metadata come from the GitHub repository API. Figures are dated snapshots. Some CLIs live inside larger repositories, so their statistics describe the whole repository. Stars measure interest, not agent compatibility.

Some projects include commercial components or connect to paid services. Follow the project’s documentation for installation, licensing, and service requirements. Unknown licenses link back to the repository.

How charts are tracked

Star charts use daily snapshots of GitHub’s total star count. Growth is the change between recorded observations, including both added and removed stars. A new listing starts with one observation; no historical growth is invented. The chart labels the actual period recorded.

Commit charts use GitHub’s weekly participation statistics. Small charts show the latest 12 weeks, each with its own vertical scale. The latest week may be incomplete. These charts show repository activity, not the CLI’s usage.

Homebrew installation counts

For verified Homebrew packages, we show explicitly requested installation events over 30, 90, and 365 days from the Homebrew formula API. These are install-on-request totals, including returned package variants such as HEAD builds. Dependency-only installations are excluded. Each card links to its specific package.

Counts cover Homebrew installations that report analytics, not unique users or total CLI adoption. The windows overlap and must not be added together. Other package managers, third-party taps, casks, separately versioned formulae, and other packages in the same repository are outside this coverage. See Homebrew’s analytics methodology.

Cards show when the snapshot was checked and the source generation date when provided. A failed refresh keeps the last successful observation and labels it as saved data. Missing analytics show “Unavailable”; CLIs without a verified formula mapping have no card. Neither case implies zero usage. Counts are refreshed with the directory snapshots.

Your saved CLIs

Bookmarks stay in this browser. There is no account to create and no cross-device sync. Clearing browser storage removes your saved list.