Six Agent Harness Capabilities for Higher Model Performance
NOOA is an open-source, object-oriented agent framework where agents are single Python classes with methods as capabilities, fields as state, and docstrings as prompts, using type annotations as enforced contracts. It introduces six key interface ideas: typed input/output, pass-by-reference, code as action, programmable loop engineering, explicit object state, and model-callable harness APIs. NOOA features a long-term memory subsystem that stores knowledge in a human-readable SQLite database, en
Analysis
TL;DR
- NOOA is an open-source, object-oriented agent framework where agents are single Python classes with methods as capabilities, fields as state, and docstrings as prompts, using type annotations as enforced contracts.
- It introduces six key interface ideas: typed input/output, pass-by-reference, code as action, programmable loop engineering, explicit object state, and model-callable harness APIs.
- NOOA features a long-term memory subsystem that stores knowledge in a human-readable SQLite database, enabling persistent, typed, relational memory without automatic summarization pipelines.
- Across benchmarks (SWE-bench Verified, CyberGym L1, ARC-AGI-3), NOOA achieves state-of-the-art performance with higher accuracy and lower token cost compared to prior harnesses.
- Agent development becomes traditional software development—agents can be diffed, tested, versioned, and refactored using standard tools.
Why It Matters
This article highlights that harness architecture—not just model choice—is critical for AI agent performance, with design choices causing double-digit swings in benchmark results and significant differences in token cost. For practitioners and researchers, NOOA provides a reproducible, inspectable, and extensible framework that bridges the gap between LLMs and structured software engineering, enabling more reliable, maintainable, and efficient agent systems. Its open release by NVIDIA Labs invites community adoption and innovation, setting a new standard for how agents should be designed and evaluated.
Technical Details
- Agent Structure: Agents are defined as single Python subclasses of
Agent, where methods represent capabilities, fields represent state, docstrings serve as prompts, and type annotations act as runtime-enforced contracts. Methods marked with ellipses (...) are completed at runtime via LLM-driven loops. - Six Interface Ideas:
- Typed Input/Output: All agentic calls use validated typed arguments and return values instead of free text.
- Pass by Reference: Models operate on live Python objects, receiving bounded previews rather than serialized dumps.
- Code as Action: The model acts by generating executable Python code with control flow and inline method calls.
- Programmable Loop Engineering: Orchestration loops are ordinary Python, writable by developers or the model itself.
- Explicit Object State: Durable, typed state resides on the agent object, not just in conversation history.
- Model-Callable Harness APIs: Context blocks and event history are exposed as APIs the model can inspect and manage.
- Memory System: Long-term memory is stored in a human-readable SQLite database. Records include types, importance tags, and relationships (e.g., “supports”, “contradicts”). A background reflection pass merges duplicates, links related records, distills insights, and prunes obsolete data. Memories can reference live agent state and are shared across sessions without retraining.
- Benchmarks & Performance:
- SWE-bench Verified: Achieves 82.2% success rate with GPT-5.5 (above SOTA of 79.2%) and 79.8% with Opus 4.6 using a general-purpose 253-line agent.
- CyberGym L1: Solves 86.8% with GPT-5.5, outperforming most closed-source systems; runs with network access blocked and rule-based validation to ensure reasoning from code alone.
- ARC-AGI-3: Demonstrates improved reasoning capability through memory accumulation (+11.8 RHAE points over file-based notes).
- Open Release: Code, data, evaluations, and benchmark agents are publicly available for reproducibility, extension, and community challenge.
Industry Insight
The NOOA framework signals a shift toward treating AI agents as first-class software artifacts—emphasizing modularity, testability, and maintainability over monolithic prompt-engineering approaches. Practitioners should prioritize harness design as a core component of agent development, leveraging typed interfaces and persistent memory to improve reliability and reduce token costs. As open-source frameworks like NOOA mature, we can expect increased standardization in agent architecture, faster iteration cycles, and broader adoption of LLM-powered agents in production environments where transparency and auditability are essential.
Disclaimer: The above content is generated by AI and is for reference only.