<img src="assets/banner.svg" alt="nushell" height="70">

# nushell

Use Nushell when Pi needs structured pipelines or when you prefer Nu syntax over Bash or PowerShell.

![nushell demo: the agent queries files with a Nu pipeline and gets a table, then the human toggles shells mid-session](assets/demo.gif)

## Use

Install `nu`, then enter `/nushell on` inside Pi.
Pi replaces its active Bash and PowerShell tools with direct `nu`.
Ask Pi to work normally, and it uses Nushell syntax for shell work.
Use `/nushell off` to restore the shell tools that were active before enabling Nushell.
Fresh `nu` does not replace shell tools by default.

Use `/nushell on` for this session, or start Pi with `--nushell` when you want it enabled from the start.
You can also make startup activation persistent in Pi settings:

```json
{
  "nushell": { "enable": true }
}
```

Each `nu` request runs in a fresh Nu process.
For Nu's native MCP server, configure `nu --mcp` separately through Pi's MCP setup; this extension does not provide an MCP wrapper.

If `nu` is missing from `PATH`, Pi leaves your current shell tools unchanged and shows a warning.
Turning Nushell off does not undo filesystem changes made by commands.

[Installation](../../README.md#install)

## Reference

<!-- config:start -->
### Commands

| Command | Purpose |
| --- | --- |
| `/nushell` | Toggle fresh Nushell tools and replace active bash/powershell |

### Setting names

| Setting | Environment | CLI flag |
| --- | --- | --- |
| `nushell.enable` | `PI_NUSHELL_ENABLE` | `--nushell` |
<!-- config:end -->