Fetching from the wire…
Public story · 2026-07-25 · high
Paul Furgale and 14 NVIDIA co-authors pitch it as a straight swap for graph and DAG orchestration, testable with pytest.
Why now: NOOA is part of the July 25 briefing, arguing agents should be built as Python objects rather than routed through graph or DAG orchestration.
NVIDIA researchers turned the AI agent into a plain Python object in a new paper called NOOA, with Paul Furgale leading 14 co-authors.
For teams building agents, the bet is that ordinary testing and debugging tools should work on agent behavior too. NVIDIA backs it with results across three benchmarks: SWE-bench Verified, Terminal-Bench 2.0, and ARC-AGI-3.
NOOA maps the object model directly onto agent design. A method is an action the model can take. A field holds state.
Docstrings work as the prompts that steer each action, and type annotations become contracts the model has to satisfy before a call goes through.
The design also combines typed inputs and outputs, pass-by-reference access to live objects, and code as the action space itself.
Agents built this way control their own loop logic instead of following a fixed graph. They hold state in explicit fields, and they can call harness APIs directly to pull context or fire events.
I like this more than I expected to. A NOOA agent is a Python class with typed methods, which makes it testable with pytest instead of a mocked graph runtime. The benchmark scores are secondary. What's worth watching is whether other agent frameworks quietly borrow the object model, or keep betting orchestration needs a layer of its own.
Each link below shares sources, entities, or timing with this story.
NVIDIA released Nemotron / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (NVIDIA released Nemotron); both cover Bench, NVIDIA, Terminal; reported by the same outlet (arxiv.org).
NVIDIA invested in Together AI / Shared entities / Earlier coverage
Linked by a graph relationship (NVIDIA invested in Together AI); both cover APIs, Bench, SWE, Terminal; earlier APIs coverage from 2026-07-08.
NVIDIA uses Claude Code / Shared entities / Same source domain
Linked by a graph relationship (NVIDIA uses Claude Code); both cover AGI, ARC, Bench, Python; reported by the same outlet (arxiv.org).
Anthropic uses NVIDIA / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (Anthropic uses NVIDIA); both cover AGI, ARC, SWE; reported by the same outlet (arxiv.org).
NVIDIA uses Codex / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (NVIDIA uses Codex); both cover AGI, ARC, SWE; reported by the same outlet (arxiv.org).
Anthropic uses NVIDIA / Shared entities / Earlier coverage / Tension
Linked by a graph relationship (Anthropic uses NVIDIA); both cover Bench, SWE, Terminal; earlier Bench coverage from 2026-04-21.
Cursor partners with NVIDIA / Shared entities / Earlier coverage / Tension
Linked by a graph relationship (Cursor partners with NVIDIA); both cover Bench, SWE, Terminal; earlier Bench coverage from 2026-07-14.
NVIDIA invested in OpenAI / Shared entities / Earlier coverage / Tension
Linked by a graph relationship (NVIDIA invested in OpenAI); both cover Bench, SWE, Terminal; earlier Bench coverage from 2026-04-25.