A modern, cross-platform shell that treats data as structured tables instead of plain text.
Nushell (often called Nu) is a modern, cross-platform shell that treats data as structured tables instead of plain text. It reimagines the command-line experience by allowing users to work with typed data—like JSON, CSV, or TOML—directly in pipelines, making it easier to filter, transform, and analyze information without complex text parsing.
Developers, data engineers, and power users who frequently work with structured data on the command line and want a more intuitive, powerful alternative to traditional shells like Bash or Zsh.
Nu offers a unique blend of traditional Unix pipeline philosophy with structured data handling, reducing the need for error-prone text manipulation. Its cross-platform design, plugin ecosystem, and focus on modern usability make it a compelling upgrade for daily command-line workflows.
A new type of shell
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Commands output data as typed tables (e.g., `ls` returns columns for name, type, size), enabling intuitive filtering and transformation without error-prone text parsing.
Officially supports Windows, macOS, and Linux with maintained compatibility for platform-specific executables, as highlighted in the goals section.
Automatically recognizes and loads structured formats like JSON, TOML, and YAML as typed data, shown in the `open Cargo.toml` example for direct exploration.
Supports plugins via a JSON-RPC protocol, allowing community extensions with examples in the `crates/nu_plugins_*` directories and a curated list in awesome-nu.
Admitted as a minimum-viable-product in the status section, meaning some commands may be unstable or buggy, unsuitable for reliability-sensitive tasks.
The plugin repository (awesome-nu) is growing but smaller than mature shells', reducing out-of-the-box functionality compared to Bash or PowerShell.
Nu's design is subject to change as it matures, potentially disrupting workflows for users who rely on consistent command behavior.