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

Citty review

Free#45 of 60 in Command-Line Interface Frameworks

A focused, typed framework for building composable Node.js command-line interfaces.

4.7/10Editor score
Citty4.7 Visit Citty

Reviewed by iTechGuides Editors · Editorial team · Updated Nov 2026

Citty is an open-source command-line interface framework for Node.js, maintained by UnJS. It targets developers building typed command trees, from small utilities to larger CLIs with nested commands and reusable plugins. The project is distributed as the npm package `citty`, uses TypeScript-oriented command definitions, and is licensed under MIT. Its published fit spans solo developers, small teams, mid-market organizations and enterprises that want a library rather than a finished command application.

The open-source model provides a free plan and keeps the pricing story straightforward. Citty’s core is a typed `defineCommand` helper with parsing for positional, string, boolean and enum options. Commands can contain recursively defined or lazily loaded subcommands, while generated usage and help output reduce repeated interface wiring. Built-in `--help` and `--version` flags cover common command behavior. Setup and cleanup lifecycle hooks apply to commands, and composable plugins expose their own setup and cleanup hooks. The `runCommand` and `parseArgs` APIs also support programmatic control when a CLI needs to be embedded in a broader process.

Platform fit is centered on Node.js and the UnJS public GitHub repository, with documentation listed as the support channel. Citty is a good choice when typed command definitions, nested loading and plugin composition are the main requirements. Its scope is narrower for teams that expect shell completion, configuration-file handling or environment-variable bindings as built-in parts of the framework. Those projects should compare alternatives that prioritize those capabilities. Teams wanting a lightweight, MIT-licensed foundation for composable TypeScript-oriented commands should find Citty aligned with that focus.

Citty pros and cons

  • Where it wins
    • Typed definitions and parsing for positional, string, boolean and enum options
    • Nested subcommands support recursive and lazy loading
    • Lifecycle hooks, plugins and programmatic command APIs
  • Where it doesn't
    • Shell completion sits outside the documented feature set
    • Configuration-file and environment-variable bindings are outside its stated scope
    • Support is provided through documentation channels

Citty 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