# Zro CLI

> Updated 2026-09-25 · type: tool · category: ai-infrastructure · status: active · rev 1

Zro CLI runs existing agent harnesses — Claude Code, Codex, OpenCode, Hermes — against open models from the command line.

- Open source: yes (MIT)
- Self-hostable: yes
- Pricing model: free
- Best for: An engineer already using a coding harness (Claude Code, Codex, OpenCode, Hermes) who wants to run it against open-weight models instead of a single proprietary backend — model portability without changing the harness they know.
- Last verified: 2026-09-25

- **Canonical:** https://gtmstacker.com/registry/tool/zro-cli/
- **Source:** [moonmath-ai · GitHub](https://github.com/moonmath-ai/zro)
- **Tags:** ai-infrastructure, mcp-agents, self-hostable, cli, model-portability, open-models
- **Repository:** https://github.com/moonmath-ai/zro

## Is Zro CLI open source?

Yes, Zro CLI is open source under the MIT license.

## How much does Zro CLI cost?

Zro CLI is free to use.

## Can I self-host Zro CLI?

Yes, Zro CLI can be self-hosted (the source is available under the MIT license).


---

Zro CLI is an MIT-licensed command-line tool that runs your existing agent harnesses — Claude Code, Codex, OpenCode, Hermes — against open models, so you can point the coding harness you already use at an open-weight backend. It is self-hostable and early: 2 stars, near-zero traction, created 2026-07-22, last pushed 2026-09-24.

## Provenance

- MIT (OSI-open); 2 stars, created 2026-07-22, last push 2026-09-24; a CLI to run existing agent harnesses (Claude Code, Codex, OpenCode, Hermes) against open models; self-hostable (WebFetch 2026-09-25).
- Surfaced via the 2026-09-25 X viral-posts brief (cross-corroboration).
- Anti-hype note: near-zero traction at 2 stars — represented as early. Harness/model support breadth is the project's claim; verify the pair you need.
- Curated from the GTM Stacker signal registry (2026-09-25 pass); license/facts independently verified 2026-09-25.

## Why it matters for a GTM stack

Teams standardize on a coding harness — Claude Code, Codex, OpenCode, Hermes — but that usually locks the model behind it too. Zro CLI's angle is model portability: keep the harness your team already knows and point it at open models from the command line, so the backend becomes a choice rather than a fixed dependency. For a team weighing cost, data-control, or self-hosted inference, being able to swap the model without swapping the workflow is the useful lever. The honest read: at 2 stars this is early and lightly proven, and the exact breadth of harness and model support is the project's own claim — so test the specific harness/model combination you care about before you rely on it in a real workflow.