Skip to content
Preprint

NVIDIA-labs OO Agents: Native Python Object-Oriented Agents

Jul 2026 · 0 citations · 62 references
Computer Science

TL;DR

Six model-facing ideas are identified that NOOA is, to the authors' knowledge, the first to combine on a single surface: typed input/output, pass-by-reference over live objects, code as action, programmable loop engineering, explicit object state, and model-callable harness APIs for context and events.

Abstract

Traditional agent development is split across prompt templates, tool schemas, callback code, and workflow graphs. We present NVIDIA Object-Oriented Agents (NOOA), a model-agnostic Python framework for building reliable AI agents. NOOA takes a simpler approach: an agent is a Python object. Its methods are the actions the model can take, fields are its state, docstrings are its prompts, and its type annotations are contracts. A method whose code body consists of"..."is completed at runtime by an LLM-driven agent loop, while methods with normal bodies remain standard deterministic Python. This gives developers and agents the same interface, so agent behavior can be tested, traced, refactored, and improved just like other software. This paper makes three contributions. (1) We present the agent-as-a-Python-object programming model and the design principles behind it. Where Python has existing abstractions, we adopt them directly. Agent-specific capabilities--context, events, state rendering, long-term memory, and validated LLM loops--are exposed through simple Pythonic APIs, so both developers and agents share one familiar programming model. (2) We identify six model-facing ideas that NOOA is, to our knowledge, the first to combine on a single surface: typed input/output, pass-by-reference over live objects, code as action, programmable loop engineering, explicit object state, and model-callable harness APIs for context and events. We find the community already converging on several of these ideas--often as experimental or partial features--and present the comparison to encourage further adoption. (3) We demonstrate that current models use this interface effectively, both in targeted capability tests and on agentic and reasoning benchmarks such as SWE-bench Verified and Terminal-Bench 2.0 and ARC-AGI-3.

View source

Similar papers

Beyond the Shell: Extending Agents with Reactive Python Notebooks

A design pattern is introduced that lets a coding agent work inside the environment directly, and marimo’s rules accumulate the agent’s exploration into a runnable, reproducible Python program.

Trevor Manz, Myles Scolnick · 0 citations
Preprint Jul 2026

Agentao: A Policy-Governed Runtime Harness for Embeddable Tool-Using LLM Agents

Agentao is presented, a governed local-first runtime for tool-using LLM agents that separates model-generated action proposals from host-authorized execution through a layered architecture consisting of host-facing surfaces, a host contract, a runtime core, a permission-mediated tool system, and supporting subsystems f...

Bo Jin, Q. Jiao, Xin Tong · 1 citation
Book Open access Jul 2026

Agent-Agnostic End-to-End C/C++ Application Performance Optimization

A code agent-agnostic agentic scaffold for automated code performance optimization that enables the system to autonomously execute the entire pipeline: project-level runtime analysis, hotspot identification and benchmark extraction, Abstract Syntax Tree (AST)-precise code localization, candidate patch generation, funct...

Hanning Lu, Chunwei Xia · 0 citations
Preprint Jul 2026

ToFu: A White-Box, Token-Efficient Agent Harness for Researchers

ToFu is presented, an agentic harness for researchers that reads your codebase, edits files, runs commands, and integrates with your development tools and provides a white-box agentic harness that allows researchers to inspect, modify, and evaluate its orchestration logic, tool-use behavior, and harness design.

Junhao Ruan, Yuan Ge, Bei Li et al. · 0 citations
Jul 2026

Authoring Agent Skills: A Software-Engineering Approach

This note argues that a skill is a software artefact and that its construction should follow software-engineering principles, with qualifications: single responsibility, separation of interface from implementation, low coupling, and economy in a shared token budget, together with behavioural evaluation in place of dete...

Giuseppe Destefanis · 1 citation
Preprint Jul 2026

Harness Handbook: Making Evolving Agent Harnesses Readable,Navigable, and Editable

The capability of a modern AI agent depends not only on its foundation model but also on its harness, which constructs prompts, manages state, invokes tools, and coordinates execution. As models, APIs, environments, and requirements evolve, the harness must be continually modified. Before such a change can be made, a d...

Ruhan Wang, Yucheng Shi, Zongxia Li et al. · 7 citations

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.