Luigit
repositories / pi-ext

pi-ext

bugabingas pi extensions

owned by admin

extensions/nushell/README.md

Raw
Rendered preview
nushell

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 Nu pipelines, then toggles Nushell off and back on

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, or start Pi with --nushell when you want it enabled from the start. Resumed sessions keep active Nu and remember which shell tools /nushell off should restore. Without startup activation, native tool selection is retained; selecting nu directly does not claim shell-replacement ownership for /nushell off. --nushell or nushell.enable: true can activate Nu after additive CLI modifiers; use an explicit tool allowlist or --exclude-tools nu to forbid activation. After /nushell off, send another prompt before exiting so Pi records the restored tools; otherwise resuming can reactivate Nu from the last request. You can also make startup activation persistent in Pi settings:

{
  "nushell": { "enable": true }
}

Each nu request runs in a fresh Nu process. Recognized parser errors can include up to 8 KiB of installed help, separately from the original command output and exit status. Help lookup has a one-second subprocess budget and does not rerun the command. Analysis accepts normal Nu source, including definitions, imports, and multi-statement scripts, without replaying runtime statements. Errors without an unambiguous installed-help target are left unchanged. 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

Reference

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
<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 Nu pipelines, then toggles Nushell off and back on](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`, or start Pi with `--nushell` when you want it enabled from the start.
Resumed sessions keep active Nu and remember which shell tools `/nushell off` should restore.
Without startup activation, native tool selection is retained; selecting `nu` directly does not claim shell-replacement ownership for `/nushell off`.
`--nushell` or `nushell.enable: true` can activate Nu after additive CLI modifiers; use an explicit tool allowlist or `--exclude-tools nu` to forbid activation.
After `/nushell off`, send another prompt before exiting so Pi records the restored tools; otherwise resuming can reactivate Nu from the last request.
You can also make startup activation persistent in Pi settings:

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

Each `nu` request runs in a fresh Nu process.
Recognized parser errors can include up to 8 KiB of installed help, separately from the original command output and exit status.
Help lookup has a one-second subprocess budget and does not rerun the command.
Analysis accepts normal Nu source, including definitions, imports, and multi-statement scripts, without replaying runtime statements.
Errors without an unambiguous installed-help target are left unchanged.
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 -->