NemoClaw-Installer
Terminal wrapper for NVIDIA NemoClaw installer
nemoclaw-installer downloads and runs the NemoClaw bash installer directly in your terminal with full PTY support. Arrow keys, interactive prompts, and selections work natively.
Features
- Native Terminal PTY: Runs directly in your terminal — no web interface needed
- Full Interactive Support: Arrow keys, dropdowns, checkboxes, password prompts all work
- Cross-Platform: Works on Windows (WSL/Git Bash), Linux, and macOS
- Multi-Architecture: Supports x86_64, ARM64, and other platforms via the native installer
- Auto-Download: Automatically downloads the latest NemoClaw installer
- Minimal Dependencies: Only requires
requests
Installation
pip install nemoclaw-installer
Usage
# Run the installer
nemoclaw-installer
# Or
python -m nemoclaw_installer
The installer will:
- Download NemoClaw installer (cached for 1 hour)
- Launch it in your terminal with full interactive support
- Run the complete NemoClaw setup with all prompts
Platform-Specific Notes
Linux & macOS
NemoClaw installs to ~/.local/bin/nemoclaw by default.
Running NemoClaw:
# The installer should add nemoclaw to your PATH
# You may need to restart your terminal or run:
source ~/.bashrc # or ~/.zshrc for zsh
# Then use nemoclaw
nemoclaw my-assistant connect
If nemoclaw command not found:
# Add to PATH manually (add to your ~/.bashrc or ~/.zshrc)
export PATH="$HOME/.local/bin:$PATH"
# Or run with full path
~/.local/bin/nemoclaw my-assistant connect
Windows
On Windows, NemoClaw is installed inside the Linux environment (WSL) or Git Bash, not in Windows itself.
Bash Selection Priority
- WSL2 (preferred) - if
wsl --versionsucceeds - Git Bash (fallback) - if found in standard locations
Running NemoClaw from Windows
From PowerShell/CMD:
# Use 'wsl' prefix to access the Linux-installed command
wsl nemoclaw my-assistant connect
From WSL terminal:
# Enter WSL first
wsl
# Then run directly
nemoclaw my-assistant connect
Accessing the Dashboard
After installation, NemoClaw runs a dashboard on https://localhost:8080:
- Use
https://(not http) - it uses a self-signed certificate - Accept the security warning in your browser (normal for local development)
- Look for the full URL with token in the terminal output
Requirements
- Python: 3.8+
- Windows: WSL2 or Git Bash
- Linux: Any distribution with bash
- macOS: 10.14+ with bash or zsh
Architecture Support: x86_64, ARM64 (Apple Silicon, AWS Graviton), ARMv7, and others (handled by the native NemoClaw installer)
How It Works
┌─────────────┐ exec/spawn ┌─────────────┐
│ Terminal │ ◄────────────────► │ NemoClaw │
│ (Your │ Full PTY │ Installer │
│ Shell) │ │ │
└─────────────┘ └─────────────┘
The wrapper:
- Downloads
nemoclaw.shfrom NVIDIA - Detects the best available shell:
- Linux/macOS: Native bash/zsh
- Windows: WSL → Git Bash
- Executes the installer with your terminal's stdin/stdout
- Full PTY support ensures interactive prompts work
Troubleshooting
"nemoclaw: command not found"
Linux/macOS:
# Add ~/.local/bin to PATH
export PATH="$HOME/.local/bin:$PATH"
Windows:
# Use wsl prefix
wsl nemoclaw my-assistant connect
Dashboard certificate error
This is normal - NemoClaw uses a self-signed certificate for local development:
- Open
https://localhost:8080 - Click "Advanced" → "Proceed to localhost (unsafe)"
- Or look for the token URL in your terminal output
Installation fails / Node.js issues
The NemoClaw installer will:
- Check for Node.js v20+ (v22+ recommended)
- Install via nvm if not present
- Handle all dependencies automatically
Just let the installer run — it manages everything.
Development
# Clone repository
git clone https://github.com/nemoclaw/nemoclaw-installer.git
cd nemoclaw-installer
# Install in editable mode
pip install -e .
# Run
python -m nemoclaw_installer
License
Apache 2.0 - See LICENSE file
Metadata
Release files for nemoclaw-installer 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| nemoclaw_installer-1.0.0.tar.gz | 9.3 kB | Without provenance | Details for nemoclaw_installer-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nemoclaw_installer-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for nemoclaw_installer-1.0.0-py3-none-any.whl |
Total release size: 19.0 kB
Release files / nemoclaw_installer-1.0.0.tar.gz
| Download URL | nemoclaw_installer-1.0.0.tar.gz |
|---|---|
| Size | 9.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e81e24ef3067b511b514f5f77592b29f0d6bfa10da38abde75ccc8600dac1d0b
|
|
BLAKE2b-256 checksum How to use checksums |
921306a628ffee1073ccde4fdaa71fafbb565db7e94bb6198332200fa28eed09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.7
|
Release files / nemoclaw_installer-1.0.0-py3-none-any.whl
| Download URL | nemoclaw_installer-1.0.0-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c7a12c8e6c5f97cc7d8edf85f46c3f5016475b514b394f7a626ea750dc5e511
|
|
BLAKE2b-256 checksum How to use checksums |
f7e9c563501eb2659cfd754214f29f5d065abedc276660d10d4ad096cc070e04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.7
|
Security for nemoclaw-installer 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.