DevOps / SRE / Platform · 04.08.2026, 16:03 UTC
Nvidia’s NOOA makes an agent one Python class
| Schweregrad | info |
|---|---|
| Kategorie | DevOps / SRE / Platform |
| Quelle | The New Stack ↗ |
| Veröffentlicht | 04.08.2026 UTC |
Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.
When Nvidia announced NOOA (Object-Oriented Agents) last week, it signaled a broader shift in agent development: The harness around a model may matter as much as the model itself.
Nvidia is contributing NOOA to the Open Secure AI Alliance, the much-written-about industry group Nvidia formed last week to build and share open-source and open-weight tools for AI development.
NOOA is founded on one idea: An agent is a single Python class. Here is how Nvidia describes it in its announcement blog post:
“Its methods are its capabilities. Its fields are its state. Its docstrings are its prompts. Its type annotations are enforced contracts. A standard Python method whose body is an ellipsis (…) is completed at runtime by an LLM-driven loop. Method with a normal body run as ordinary, deterministic Python.”
By bringing an agent’s capabilities, state, and prompts together in one Python class, Nvidia is working to solve the thorny problem that is fragmentation in agent development.
It’s an issue that Adnan Masood, Ph.D., chief AI architect, UST, sees regularly.
“The harness is everything wrapped around the model,” Masood tells The New Stack. “Today it is scattered by design. A team building on LangGraph or AutoGen typically has prompts in Jinja templates, tool definitions in JSON schemas, callbacks in Python, and the workflow drawn as a graph in yet another abstraction.”
Can one Python class make agents easier to test?
Nvidia’s idea is to make agent development more like traditional software development so both humans and AI coding agents can inspect and manage an agent …