Homebrew #

Recommended on macOS. Homebrew manages the installation and its dependencies.

macOS / Install

brew install raiseCatError/tap/nmsh
nmsh

Build from source #

This checks out the verified published release tag. Run these commands in an ordinary shell, outside NMSh.

Source / v0.20.0

git clone --branch v0.20.0 https://github.com/raiseCatError/notMyShell.git
cd notMyShell
npm install
npm run build
npm link
nmsh

Allow the required node-pty native install step. Depending on the platform, a C/C++ build toolchain and Python may be needed. The source distribution is not an npm registry installer.

Requirements #

Component	Requirement / evidence
Node.js	22+ for NMSh
Shell	zsh (default), Bash 4.4+ or Fish. macOS Bash 3.2 is too old.
macOS	Primary platform. In v0.20.0 the first-run setup and Tools flow were physically accepted; other checklist items were not recorded.
Linux	Beta. Ubuntu automated suite and Fedora subset; no physical validation yet.
Windows	WSL 2 beta path only. Run Linux Node inside WSL. Native Windows and WSL 1 unsupported.

Keep a real shell as your system/login shell. Do not set NMSh using chsh. An optional terminal launch command starts the frontend without changing your shell identity.

Detailed shell and host compatibility →

Update #

Homebrew / Update

brew upgrade raiseCatError/tap/nmsh

For a Homebrew install, /update directs you back to Homebrew rather than modifying its Cellar. For a clean official source checkout, /update shows the latest stable plan; /update apply applies it with build verification and rollback on failure. Review the plan first.

Uninstall #

Finish live work first; closing a window can leave its session running. Homebrew installations are removed through Homebrew:

Homebrew / Remove

brew uninstall nmsh

For source installations, preview NMSh's ownership-aware removal plan:

Source / Preview, then confirm

nmsh uninstall --dry-run
nmsh uninstall

The source uninstaller removes only launcher links it proves belong to NMSh and refuses while live sessions run. Do not casually delete the config directory: saved sessions and preferences live there. Review any separate data-removal choice explicitly.

Troubleshooting #

Diagnostics

node --version
nmsh --version
nmsh doctor

GUI terminals can inherit a different PATH. For Ghostty, the canonical guide gives this pattern, using paths you replace with your actual installed locations:

Ghostty config / Example paths only

command = direct:/absolute/path/to/node /absolute/path/to/nmsh

Do not paste placeholder paths unchanged. Confirm the Node executable, launcher location and host configuration before changing a launch command.

See troubleshooting, the canonical install instructions and release limitations. There are no official downloadable native installers advertised here.

Keep your shell.
Add NMSh.