NVIDIA betting on OpenClaw
At GTC 2026, Jensen Huang compared OpenClaw to Windows, calling it "the operating system for personal AI." NVIDIA then announced NemoClaw, an open-source reference stack that wraps OpenClaw with security and privacy controls. On the surface, it looks like a GPU company wandering into agent infrastructure for no reason. But look closer and the logic is airtight.
What NVIDIA actually announced
NemoClaw is a single-command installer that layers NVIDIA's own tooling on top of OpenClaw. It bundles three things together:
- NVIDIA OpenShell, a new open-source runtime that sandboxes agent execution with policy-based security guardrails
- NVIDIA Nemotron models, open-weight LLMs optimized for running locally on NVIDIA hardware
- A privacy router that lets agents call cloud-hosted frontier models when local compute isn't enough, while keeping data flows auditable
The pitch is simple: take OpenClaw, which has become the fastest-growing open-source project in history, and make it safe enough that enterprises and serious users will actually deploy it. Peter Steinberger, the creator of OpenClaw, appeared alongside Huang at the keynote, lending legitimacy to the partnership.
OpenClaw's security problem is real
To understand why NemoClaw matters, you need to understand how bad OpenClaw's security story has been. OpenClaw (which started life as Clawd in November 2025, was briefly renamed Moltbot, then settled on OpenClaw in January 2026) gives an AI agent shell access to your machine. It can run commands, read and write files, execute scripts, manage your calendar, send emails, and automate browser tasks. All of this through messaging apps like WhatsApp, Slack, and Discord. The security track record has been rough:
- A January 2026 audit found 512 vulnerabilities, eight of them critical
- Researchers discovered over 40,000 exposed OpenClaw instances on the public internet, with 63% of them vulnerable to remote code execution
- 15% of community-submitted skills (add-on packages from the skill repository) were found to contain malicious instructions designed to exfiltrate data, harvest credentials, or download payloads
- The platform has 35 documented CVEs so far, including a command injection vulnerability in the Docker sandbox
- Cisco's security research team demonstrated that a popular skill ("What Would Elon Do?") was functionally malware, silently sending user data to an external server while using prompt injection to bypass safety guidelines
- Plaintext API keys and credentials have been leaked through prompt injection and unsecured endpoints
As Cisco's researchers put it: "From a capability perspective, OpenClaw is groundbreaking. From a security perspective, it's an absolute nightmare." The platform's own documentation admits there is no "perfectly secure" setup.
So why would NVIDIA bet on this?
This is where the strategic logic gets interesting. NVIDIA isn't betting on OpenClaw despite the security mess. It's betting on OpenClaw because of the security mess, and because of what always-on agents mean for compute demand. Always-on agents need always-on hardware. This is the key insight. An agent that manages your email, books your flights, and monitors your calendar doesn't run for a few seconds and stop. It runs continuously, around the clock, consuming compute the entire time. Jensen Huang has been saying for years that the world needs more compute. Autonomous agents are the use case that proves him right in the most tangible way possible. OpenClaw already has the users. With 165,000 GitHub stars and 60,000 Discord members in just a few months, OpenClaw has achieved the kind of organic adoption that money can't buy. The most popular hardware for running it has been the Mac Mini, which means all those cycles are happening on Apple silicon, not NVIDIA GPUs. NemoClaw is NVIDIA's play to redirect that compute demand toward its own ecosystem, specifically GeForce RTX PCs, RTX PRO workstations, DGX Station, and the new DGX Spark. Security is the blocker, not capability. OpenClaw already works. People love what it can do. The reason enterprises won't touch it and cautious users stay away is the security story. By building the security layer itself, NVIDIA removes the single biggest obstacle to mass adoption, which in turn drives more demand for the hardware these agents run on. Local inference is the wedge. NemoClaw's architecture is clever. It uses Nemotron models running locally for privacy-sensitive tasks, with a router that can call cloud models for harder problems. This means the baseline compute happens on your own NVIDIA hardware, all day, every day. The more capable the local models get, the more you want better local hardware. The more tasks you delegate to your agent, the more tokens it burns. It's a flywheel.
Does NemoClaw actually fix the problems?
The honest answer is: partially. OpenShell's sandboxing is a genuine improvement. Running agents in an isolated environment with policy-based guardrails means a compromised skill can't immediately access your entire filesystem. Network traffic can be inspected and controlled. That addresses some of the most severe attack vectors. But security researchers remain cautious. As Karthik Ranganathan, CEO of Yugabyte, pointed out, NemoClaw doesn't address scenarios where the agent takes destructive actions within its authorized scope, like an email agent that starts deleting messages instead of summarizing them. The sandboxing controls where the agent can act, but it doesn't fully solve what it decides to do within those boundaries. The skill ecosystem remains a concern too. Community-contributed skills are essentially untrusted code packages that get loaded from disk. NVIDIA's guardrails help contain damage, but they don't fundamentally solve the supply chain problem of a repository where malicious actors can manufacture popularity and keep republishing flagged content under new names. Melissa Bischoping, senior director of security research at Tanium, captured the sentiment well: NVIDIA's investment is a positive signal, but agentic AI systems need more robust safety measures to truly protect users, especially given how fast this space is moving.
The bigger picture
NVIDIA's move with NemoClaw follows a pattern the company has perfected: find where compute demand is heading, build the software layer that makes their hardware the obvious choice, and open-source it so the ecosystem does the distribution work for you. CUDA did this for scientific computing. TensorRT did it for inference optimization. Now NemoClaw is doing it for autonomous agents. The bet isn't that OpenClaw will be the only agent platform. The bet is that always-on AI agents, in whatever form they take, will become one of the largest consumers of dedicated local compute. And if NVIDIA is the company that solved the security problem that unlocked mainstream adoption, it becomes very hard for that compute to happen anywhere else. Is it cynical? Maybe. But it's also exactly what the OpenClaw ecosystem needs. A well-resourced company with deep infrastructure expertise investing in making these agents safer is better than the alternative, which is millions of users running unsecured agents on exposed endpoints with no guardrails at all. The question isn't whether NVIDIA's motives are pure. The question is whether NemoClaw's guardrails are good enough. And right now, "better than nothing" is a significant upgrade over what OpenClaw users had before.
References
- NVIDIA, "NVIDIA Announces NemoClaw for the OpenClaw Community," March 16, 2026, https://nvidianews.nvidia.com/news/nvidia-announces-nemoclaw
- Daniel Howley, "Nvidia launches NemoClaw platform for AI agents," Yahoo Finance, March 16, 2026, https://finance.yahoo.com/news/nvidia-launches-nemoclaw-platform-for-ai-agents-200851962.html
- Mashable, "Nvidia NemoClaw: What it is and how to try it," March 2026, https://mashable.com/article/nvidida-nemoclaw-what-it-is-how-to-try-it
- Blake Stimac, "Nvidia's NemoClaw Promises a More Secure Way to Deploy AI Agents, but Is It Really Safer?" CNET, March 19, 2026, https://www.cnet.com/tech/services-and-software/nvidia-wants-to-make-it-easier-to-create-an-openclaw-ai-agent/
- Amy Chang, Vineeth Sai Narajala, and Idan Habler, "Personal AI Agents like OpenClaw Are a Security Nightmare," Cisco Blogs, 2026, https://blogs.cisco.com/ai/personal-ai-agents-like-openclaw-are-a-security-nightmare
- Kaspersky, "Don't get pinched: the OpenClaw vulnerabilities," 2026, https://www.kaspersky.com/blog/openclaw-vulnerabilities-exposed/55263/
- Infosecurity Magazine, "Researchers Find 40,000+ Exposed OpenClaw Instances," 2026, https://www.infosecurity-magazine.com/news/researchers-40000-exposed-openclaw/
- NVIDIA, "NVIDIA NemoClaw GitHub Repository," https://github.com/NVIDIA/NemoClaw
- NVIDIA, "Run OpenClaw For Free On NVIDIA RTX GPUs & DGX Spark," https://www.nvidia.com/en-us/geforce/news/open-claw-rtx-gpu-dgx-spark-guide/