cd /news/developer-tools/260908-2500-cli-database-open-source… · home topics developer-tools article
[ARTICLE · art-122852] src=x-cmd.com ↗ pub= topic=developer-tools verified=true sentiment=· neutral

[260908] 2500+ CLI Database Open Sourced! x-cmd v0.10.7

X-cmd v0.10.7 has been released, opening its database of over 2,500 CLI packages across 70+ categories for community contributions via PRs, including public data on project activity and footprint details such as CPU, memory, and skills. The update also adds a new AI harness 'x agent request --harness codex-ds' supporting Codex and DeepSeek, and fixes compatibility issues with the latest Codex CLI and field handling in 'x repo card'.

read4 min views1 publishedSep 8, 2026
[260908] 2500+ CLI Database Open Sourced! x-cmd v0.10.7
Image: X-Cmd (auto-discovered)

TLDR

  • x-cmd v0.10.7 Key Updates: - Open 2500+ CLI Database :x-cmd/install is now open for community PRs, sharing public data including project activity metrics andfootprint details (CPU, memory, Skill, etc.).
    • New AI Harness : Addedx agent request --harness codex-ds (supporting Codex + DeepSeek).
    • Bug Fixes : Resolved compatibility issues with the latest Codex CLI and fixed abnormal field handling inx repo card .

Recently, we released x-cmd v0.10.7.

In this update, x-cmd/install is officially open for community contributions, and everyone is welcome to submit PRs.

Currently, x-cmd/install has included over 2500+ software packages across 70+ categories, and the list continues to grow.

From "How to Install" to "How Good Is This Project" #

x-cmd/install initially served x-cmd's installation capabilities, providing installation-related data for x install.

Now, the information here has become much richer.

For example, when looking at a CLI, besides installation methods, you can also view the project description, License, latest version, creation time, recent commits, releases, as well as community metrics such as Stars, Forks, Contributors, Issues, and PRs. It also tracks code languages, codebase size, and activity over the last 30 / 90 / 180 / 360 days regarding Commits, Releases, PRs, and Issues.

This way, when evaluating a CLI, in addition to knowing "whether it can be installed", you can conveniently understand the current status of the project.

Has it been updated recently?

How many people are still participating in the community?

Are there many Issues and PRs?

Has it been unmaintained for a long time?

This information is very useful for choosing a CLI, and holds equal reference value for AI Agents looking for tools.

This data is displayed on the Install page of the x-cmd official website, and can also be directly retrieved via formats like YAML and TSV, making it convenient for other tools or Agents to consume.

Some Information Is Only Known Through Actual Use #

Data that can be automatically retrieved from upstream will continue to be updated automatically.

However, details under footprint—such as CPU, Memory, Network, Filesystem, and Skill—are somewhat special.

CPU and Memory track resource consumption during execution; Network and Filesystem record resources accessed during runtime; Skill describes what tasks the CLI can perform.

These aspects cannot always be accurately determined just by looking at the README and code in a GitHub repository.

For instance, how much memory a CLI actually consumes, which directories it accesses at runtime, or what it is typically used for in practice are details best understood by those who actively use it. Therefore, this portion of data is ideal for everyone to supplement along the way.

Filling Out the 2500+ CLI Database Together #

If you frequently use a specific CLI in your daily workflow, check if it exists in `x-cmd/install`.

If information is missing, you can fill it in; if `footprint` is not yet available, you can add it based on your actual usage; if existing data is inaccurate, feel free to submit corrections directly.

You don't need to study the entire project—just start with a tool you are familiar with.

These contributions will ultimately turn into public data. Information you supplement today might be looked up by another developer tomorrow, or serve as a reference point when an AI Agent selects a tool.

Furthermore, as more people participate, the coverage of CLIs will widen, and practical usage insights will grow richer.

We will continue handling the automated collection of upstream versions, Releases, Commits, and Issues, while everyone can join in supplementing data that isn't easily obtained through automated means.

Ultimately, we hope to build not just an installation dataset for x-cmd itself, but a CLI database that everyone can query, use, and continuously expand.

If there is a CLI you know well, welcome to submit a PR!

Other Updates in v0.10.7 #

In addition to x-cmd/install, v0.10.7 also introduces:

x agent request --harness codex-ds Now you can use Codex + DeepSeek.

We also fixed compatibility issues with the new Codex CLI and resolved abnormal field handling in x repo card.

Please indicate the source and link of this article when reprinting.

Help us make these docs great!

All X-CMD docs are generated from command help and multiple data sources. See something that's wrong or unclear? Feel free to let us know through any of these ways~

── more in #developer-tools 4 stories · sorted by recency
── more on @x-cmd 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/260908-2500-cli-data…] indexed:0 read:4min 2026-09-08 ·