NVIDIA/NemoClaw

NVIDIA/NemoClaw

Description: Run agents like Hermes and OpenClaw more securely inside NVIDIA OpenShell with managed inference

Language: TypeScript

License: Apache-2.0

Stars: 21115

Forks: 2807

Open issues: 404

Created: 2026-03-15T17:04:09Z

Pushed: 2026-06-11T02:50:22Z

Default branch: main

Fork: no

Archived: no

README:

NVIDIA NemoClaw: Reference Stack for Sandboxed AI Agents in OpenShell

NVIDIA NemoClaw is an open source reference stack for running always-on AI agents more safely inside NVIDIA OpenShell sandboxes. It provides guided onboarding, a hardened blueprint, routed inference, network policy, and lifecycle management through a single CLI.

Supported agents:

• OpenClaw (default)
• Hermes

For capabilities, architecture, security controls, and the full feature list, see the NemoClaw documentation.

Get Started

Review Prerequisites before installing. For Hermes, set NEMOCLAW_AGENT=hermes before running the installer, or use the nemohermes alias after install.

| Agent | Guide | |-------|-------| | OpenClaw (default) | Quickstart with OpenClaw | | Hermes | Quickstart with Hermes |

Documentation

Refer to the following pages on the official documentation website for more information on NemoClaw.

| Page | Description | |------|-------------| | Overview | What NemoClaw does and how it fits together. | | Architecture Overview | High-level overview of Plugin, blueprint, sandbox lifecycle, and protection layers. | | Ecosystem | How OpenClaw, OpenShell, and NemoClaw form a stack and when to use NemoClaw versus OpenShell alone. | | Architecture Details | Detailed description of Plugin structure, blueprint lifecycle, sandbox environment, and host-side state. | | Prerequisites | Hardware, software, and supported platforms, with any platform-specific pre-setup. | | Inference Options | Supported providers, validation, and routed inference configuration. | | Network Policies | Baseline rules, operator approval flow, and egress control. | | Customize Network Policy | Static and dynamic policy changes, presets. | | Security Best Practices | Controls reference, risk framework, and posture profiles for sandbox security. | | Sandbox Hardening | Container security measures, capability drops, process limits. | | CLI Commands | Full NemoClaw CLI command reference. | | Troubleshooting | Common issues and resolution steps. |

Community

Join the NemoClaw community to ask questions, share feedback, and report issues. NemoClaw is an alpha project, so maintainers review issues, discussions, and pull requests on a best effort basis without guaranteed response timelines.

| Need | Channel | |------|---------| | Setup or usage questions | GitHub Discussions or Discord | | Reproducible bugs | GitHub Issues | | Feature proposals | Start with GitHub Discussions, then open an issue when the scope is clear | | Current priorities | [Current Priorities](#current-priorities) | | Contribution help | [CONTRIBUTING.md](CONTRIBUTING.md) | | Security vulnerabilities | Use the private channels in [SECURITY.md](SECURITY.md); do not open public issues |

Contributing

We welcome contributions. See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, coding standards, and the PR process.

Security

NVIDIA takes security seriously. If you discover a vulnerability in NemoClaw, DO NOT open a public issue. Use one of the private reporting channels described in [SECURITY.md](SECURITY.md):

• Submit a report through the NVIDIA Vulnerability Disclosure Program.
• Send an email to [psirt@nvidia.com](mailto:psirt@nvidia.com) encrypted with the NVIDIA PGP key.
• Use GitHub's private vulnerability reporting to submit a report directly on this repository.

For security bulletins and PSIRT policies, visit the NVIDIA Product Security portal.

Current Priorities

NemoClaw's current priorities are maintained here as a public orientation point for contributors and community members. This list is not a delivery commitment, support promise, or fixed roadmap; priorities can change as maintainers respond to security, quality, platform readiness, and community feedback.

• Improve install and onboarding reliability across tested platforms.
• Strengthen sandbox hardening, credential handling, and network-policy defaults.
• Validate local and routed inference behavior for supported provider paths.
• Keep documentation, troubleshooting guidance, and agent skills aligned with supported workflows.

For specific scoped work, use GitHub Issues and start broader proposals in GitHub Discussions. Security vulnerabilities must use the private reporting channels in [SECURITY.md](SECURITY.md), not…