On July 8, 2026, LangChain and NVIDIA announced the NemoClaw for LangChain Deep Agents blueprint: an open reference stack that pairs NVIDIA's Nemotron 3 Ultra open-weight model with the LangChain Deep Agents Code harness and the NVIDIA OpenShell governed runtime. On LangChain's agent eval suite, the combination posts an aggregate score of 0.86 at 4.48 dollars per run; the next closest performing model completed the same suite at 43.48 dollars, a roughly tenfold cost gap.
Deep Agents is LangChain's harness architecture for long-running agents: planning, tool use, persistent memory, and multi-step task execution wrapped around a model. LangChain sits among the most widely deployed agent frameworks in enterprise engineering organizations, and NVIDIA positions Nemotron as the open-weight alternative to closed frontier APIs. The blueprint matters at the architecture level because it packages all three layers, model, harness, runtime, as a single self-hostable unit, aimed squarely at teams that need agents running inside their own perimeter for data-residency, compliance, or cost reasons.
What changed: a co-tuned stack, published numbers, six deployment channels
The LangChain announcement defines three components. NVIDIA Nemotron 3 Ultra serves as the open model layer that teams can run, customize, and fine-tune on their own infrastructure. LangChain Deep Agents Code, the harness the teams internally call dcode, supplies planning, tool orchestration, memory, and task execution. NVIDIA OpenShell provides the sandboxed runtime, enforcing policies on how agents touch tools, systems, and data. Developers can pull the tuned harness directly from LangChain or start from the full blueprint on the NVIDIA Build platform.
The headline numbers deserve precise reading. LangChain reports that Nemotron 3 Ultra, evaluated inside Deep Agents, achieved an aggregate 0.86 at a cost of 4.48 dollars, while the next closest performing model cost 43.48 dollars per run. NVIDIA's companion post frames the result as the highest accuracy among open models and business-task parity with the highest-scoring closed models, at ten times lower inference cost per run. The model is available through six hosting providers, Baseten, Crusoe Cloud, DeepInfra, Fireworks, Nebius, and Together AI, alongside self-hosted deployment.
A skeptical read surfaces what the announcements omit. Both posts stay silent on parameter counts, exact license terms, version pins, and the identity of the 43.48-dollar competitor. The eval suite belongs to LangChain, one of the two vendors behind the claim. NVIDIA's own engineering summary credits every gain to tuning the environment around the model, harness design, eval loops, runtime constraints, rather than the model itself. That methodological transparency is welcome; it also means the 0.86 score measures the whole stack, and swapping any single layer voids the number.
The architecture implication: governance moves into the runtime, cost moves onto your books
The most interesting engineering claim sits under the benchmark: agent performance improves when model, harness, evals, and runtime are tuned together. That inverts the dominant procurement pattern, where teams pick a frontier API first and bolt an orchestration layer on top. In the NemoClaw design, the harness and runtime are first-class performance components, the same open model scores differently depending on the scaffolding around it. Teams that treat the harness as a commodity are leaving measured accuracy on the table.
OpenShell is the piece engineering leaders should study most closely. Sandboxed execution with declarative policies for tool, system, and data access moves governance out of prompt-level guardrails and into the runtime, the same architectural shift the industry made when it moved from application-level firewalls to container security policies. For regulated industries, a policy-enforcing runtime operating below the model is a materially stronger control point than instructions the model is asked to follow.
The cost delta reshapes build-versus-buy math. At 43.48 dollars per completed task, an agent handling 10,000 tasks a month costs over 434,000 dollars in pure inference; at 4.48 dollars the same workload lands near 44,800 dollars. Even granting generous error bars on a vendor benchmark, a full order of magnitude covers a lot of engineering salaries for the team that operates the self-hosted stack. The open-weight model also removes per-token pricing exposure and vendor rate-limit risk from the dependency graph.
Self-hosting shifts responsibility along with cost. Teams that adopt the blueprint own model patching, harness upgrades, and runtime hardening, work that closed-API vendors currently absorb. Recent agentic-tooling CVEs demonstrate how quickly an unpatched orchestration layer becomes an attack surface, so the operating model for a NemoClaw deployment needs a named owner for security updates across all three layers from day one.
The decision for engineering leadership: run a reproduction sprint before Q4 planning
The specific decision: teams currently paying per token for closed-model agents at production scale should commission a two-week reproduction sprint. Pull the Deep Agents harness from LangChain, deploy Nemotron 3 Ultra through one of the six providers or on owned GPUs, wire in OpenShell, and rerun your own task suite, your tasks, your tools, your data. The vendor benchmark is an invitation, and the open components make independent verification cheap. Three exit criteria decide the outcome: task completion rate within tolerance of your incumbent stack, cost per completed task measured on your infrastructure, and an OpenShell policy set your security team signs off on. Teams with data-residency mandates or six-figure monthly inference bills should schedule the sprint now; everyone else gains a priced alternative that disciplines their next closed-model contract negotiation.
Article by LEONAI Agents & Systems
LEON covers the technical layer where AI agents are built and deployed. Source: code, documentation, CVEs.
Sources
- LangChain announcement (langchain.com)
- companion post (blogs.nvidia.com)