Open-source project
nushell/nushell avatar
nushell/nushell

Nushell: A Structured Data Shell That Rethinks the Pipeline

GitHub describes it as A new type of shell. The repository metadata lists Rust as its primary language. The metadata lists the MIT license. This article stays within the project description and details documented in the GitHub repository README.

41,018 stars2,350 forksRustMIT

At a glance

What is it?
Nushell turns shell output into structured data, not raw text. This review covers its pipeline model, configuration, plugins, and where it falls short for traditional Unix users.
Who is it for?
Adopt Nushell if you work with JSON, TOML, or tabular data and want a shell that treats output as data, not text. Skip it if you depend on POSIX shell scripts.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly Rust, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • nushell/nushell41,018 ★ · +759
Star history
Repository2026-08-132026-11-15
nushell/nushell40.3k41k

759 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The Problem: Shells That Discard Structure

Traditional shells like bash and zsh treat everything as a stream of bytes. When you run ls, you get a formatted string, and parsing that string with awk or sed is fragile. Nushell attacks this problem by making structure first-class. Commands can output structured data: tables, records, lists. The README shows that ls returns a table with columns for name, type, size, and modified time. This is not a cosmetic change. It means you can filter, sort, and extract fields with commands that understand the data, not the text representation. The intended user is someone who spends hours in a terminal manipulating files, processes, and configuration data, and who is tired of writing brittle text parsers.

How Nushell's Pipeline Actually Works

The core mechanism is the pipeline, but with a twist. In Unix, you pipe bytes. In Nushell, you pipe values. The README describes three categories of commands: producers (like ls), filters (like where), and consumers (like table). The where command works on the structured stream, so `ls | where type == "dir"` filters rows without any text parsing. The same where command works on ps output: `ps | where cpu > 0`. This uniformity is powerful. You learn one filtering syntax and apply it to any command that outputs structured data. This is a fundamental shift from the text-centric Unix model, and it changes how you think about composing commands.

Getting Started: Install and First Commands

Installation is straightforward. On Linux and macOS, the README recommends `brew install nushell`. On Windows, use `winget install nushell`. There is also a GitHub Action named setup-nu for CI. After installation, the first run creates a default config file. The README points to sample_config in the repository, and you can find your config path by running `$nu.config-path`. The configuration is a Nushell script, not a plain text file. That means you can write logic in your config, like conditionals or loops. You can customize it from there. The book is the primary documentation, and there is a cookbook with examples.

Opening Files as Data, Not Text

One of the most distinctive features is the open command. When you run `open Cargo.toml`, Nushell parses the TOML and returns a record. The README shows the output as a table with fields like bin, dependencies, and package. You can then drill down with `get package.version` to get a specific value. This works for JSON, YAML, and other formats that Nushell recognizes. This is a major time-saver. Instead of using jq or yq, you use the same pipeline commands you already know. The limitation is that open only parses recognized formats. For unknown formats, it falls back to raw text, which is fine. But the power is undeniable when you are exploring a new project's configuration or API response.

Plugins: Extending the Model, Not the Syntax

Nushell supports plugins, but they are not like bash function libraries. Plugins are separate binaries that communicate with the shell using the structured data model. The repository workspace includes crates named nu_plugin_*, such as nu_plugin_polars and nu_plugin_gstat. This means a plugin can output a table, and you can filter it with where, just like built-in commands. This is a clean design. It avoids the mess of parsing text output from external tools. However, it also means that a plugin must be written to Nushell's protocol, not just a shell script. That raises the barrier for contributors. You cannot simply wrap an existing CLI tool and have it work seamlessly. The plugin must understand the structured data protocol, which is more work than a typical shell script.

Limitations and Failure Modes

The README is honest: the project has reached minimum-viable-product level, but it may be unstable for some commands. The design is subject to change. That is a warning for production use. If you rely on a specific command, it might change behavior in a minor release. Another limitation is compatibility. Nushell's syntax is not POSIX. Your .bashrc and shell scripts will not work. You must rewrite them in Nushell's language. For complex scripts, that is a significant effort. Nushell is not a drop-in replacement. It is a new environment. If you live in a world of legacy scripts and tools that parse text, Nushell will fight you.

Alternatives: PowerShell and Text-Based Shells

The closest alternative is PowerShell, which also treats output as structured objects. PowerShell is mature on Windows, with deep integration into .NET and the Windows management stack. Nushell is cross-platform and lighter, written in Rust, and its data model is simpler than PowerShell's object model. The difference in approach: PowerShell uses objects with methods and properties, while Nushell uses tables and records that you manipulate with pipeline commands. For Unix users, the alternative is to stay with bash or zsh and use text tools like jq for JSON. That approach is familiar but requires learning a separate tool for each format. Nushell unifies that. If you are already comfortable with jq and awk, you may not need Nushell. But if you want a single shell that handles structured data natively, Nushell is a stronger fit than PowerShell for non-Windows users.

Maintenance, Licensing, and Upgrade Cost

The repository is actively maintained, with recent releases in 2026. The license is MIT, which is permissive for commercial use. The upgrade cost is real. Because the design is still evolving, new releases may introduce breaking changes. The README says the design is subject to change as it matures. That means you should read the changelog before upgrading. The config files are code, so you need to maintain them like code. The documentation is solid, with a book and a cookbook, but the command list is long, and learning the Nushell language takes time. If you adopt Nushell, budget time for learning and for adapting to changes.

Editorial conclusion

Adopt Nushell if you work with JSON, TOML, or tabular data and want a shell that treats output as data, not text. Skip it if you depend on POSIX shell scripts. Before adopting, verify that your daily commands are available as Nushell built-ins or plugins, and test your existing shell scripts for compatibility, since Nushell's syntax and data model differ fundamentally from bash.

Frequently asked questions

What is Nushell used for?

It is a shell that treats input as structured data rather than raw streams of text. Listing a directory returns a table of rows, commands fall into three roles that produce, filter and consume a stream, and files and URLs can be loaded as raw text or as structured data when the format is recognized, so `open Cargo.toml | get package.version` returns a single value.

Is Nushell a shell or a language?

The file calls it a shell, describing it as a new type of shell, and says it draws inspiration from PowerShell, functional programming languages, and modern CLI tools. It is distributed as a Rust crate named nu with a default run target of nu, and it is not presented as a general-purpose programming language.

Is Nushell written in Rust?

Yes. Rust is the primary language, the workspace sets edition 2024 and rust-version 1.97.1, and the repository carries a rust-toolchain.toml alongside rustfmt.toml and clippy.toml. The shell is published to crates.io as the crate nu.

Can Nushell be used as a daily driver?

The status section says many people use it as their daily driver, but it may be unstable for some commands, and that the design is subject to change as it matures. It also states the project has reached a minimum-viable-product level of quality, and the Cargo manifest version is 0.116.2.

is nushell posix

Nushell is not a POSIX shell: its pipelines carry structured data. The README says commands are separated by the pipe symbol to denote a pipeline flowing left to right, that commands output to stdout and read from stdin, and that they can also output structured data as a third kind of stream.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/nushell-nushell.svg)](https://hysenlabs.com/projects/nushell-nushell)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/nushell-nushell.svg)](https://hysenlabs.com/projects/nushell-nushell)

Was this useful?