Homebrew #
Recommended on macOS. Homebrew manages the installation and its dependencies.
+ {release.tapVersion !== `v${launch.version}` && }
+ Build from source #
{launch.state === 'candidate' ? 'This checks out the exact public candidate commit used by these docs. It is not a published release. The final tag will replace this checkpoint after release validation.' : 'This checks out the verified published release tag.'} Run these commands in an ordinary shell, outside 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 | {release.requirements.node} 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 #
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.
The detached candidate checkout above is for review. Do not use the stable updater to advance between candidate commits. Use a fresh checkout of the next explicitly reviewed commit instead.
} +Uninstall #
Finish live work first; closing a window can leave its session running. Homebrew installations are removed through Homebrew:
For source installations, preview NMSh's ownership-aware removal plan:
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 #
GUI terminals can inherit a different PATH. For Ghostty, the canonical guide gives this pattern, using paths you replace with your actual installed locations:
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.
+