Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

dry-cli review

Free#49 of 60 in Command-Line Interface Frameworks

A focused Ruby toolkit for structured commands, options, subcommands, and completion.

4.3/10Editor score
dry-cli4.3 Visit dry-cli

Reviewed by iTechGuides Editors · Editorial team · Updated Nov 2026

dry-cli is an open-source Ruby framework for developing command-line interface applications. It models each command as an object and registers those objects in a command registry, giving Ruby developers a structured way to define command trees. The framework supports required, optional, and array positional arguments; named options with booleans, arrays, defaults, aliases, and allowed values; nested subcommands; and command or option help output. It fits solo developers through enterprise teams that want a focused Ruby command layer rather than a general application platform.

The pricing model is straightforward: dry-cli is distributed as an open-source Ruby gem under the MIT license, with a free plan. The published feature set centers on command-definition depth instead of paid-tier separation. Variadic argument forwarding lets a parent command pass trailing arguments to a subcommand, while callbacks cover the command execution lifecycle. Those capabilities suit tools with multi-level commands, aliases, constrained option values, or shared execution hooks. A completion-generation example is provided for Bash and Zsh, helping teams connect the command model to common shell workflows.

Integration breadth is narrower than the command model itself. The project is maintained in the dry-rb GitHub organization by the Hanakai team, and support channels are documentation and community. Its documented ecosystem focus is Ruby, so teams building CLIs in another language should choose a framework native to that language. Likewise, projects needing integrations beyond command parsing, or completion coverage outside the demonstrated Bash and Zsh examples, may need additional tooling. Choose dry-cli when a lightweight registry and typed command structure matter most; look elsewhere when a broader platform ecosystem is the primary requirement.

dry-cli pros and cons

  • Where it wins
    • Registry-based command objects organize hierarchical CLI designs.
    • Handles positional, named, boolean, array, aliased, and constrained values.
    • Generates help and completion with variadic forwarding and lifecycle callbacks.
  • Where it doesn't
    • Ruby-focused, so non-Ruby projects need another framework.
    • Support is centered on documentation and community channels.
    • Documented completion guidance targets Bash and Zsh.

dry-cli fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update