Large language model (LLM) agents increasingly undertake long-horizon tasks that require sustained reasoning, tool use, and revision across many interdependent steps. However, existing agent harnesses maintain task execution, task state, and completion assessment within a growing context, making the state difficult to track and allowing incorrect self-assessments to propagate into later decisions. We reformulate long-horizon execution as a task-state management problem and propose LongHorizon-Harness, which maintains the task state explicitly outside execution and updates it only with facts independently verified from the environment. Its Manage-Execute-Audit(MEA) loop uses a manager to maintain the task state and determine the next subtask, a fresh-context executor to perform it, and a read-only auditor to verify the resulting environment state before the next round. A lightweight AgentAdapter supports interchangeable model and harness backends without modifying their native agent loops. LongHorizon-Harness improves Qwen~3.7-Plus from 51.8% to 80.7% on WeaveBench, from 69.7% to 77.2% on Terminal-Bench~2.1, and from 2.8% to 8.3% on OSWorld~2.0. It also raises Claude Opus~4.7 from 20.0% to 34.3% on an OSWorld2.0 subset, demonstrating consistent gains across models, harnesses, and interaction domains.
Alex: Welcome to another episode of ResearchPod. Today, we're looking at a new way to help AI agents finish complex, multi-step projects without getting lost or making mistakes along the way.
Sam: We're discussing a research paper about a framework called "LongHorizon-Harness." The central claim is that AI agents often fail at long tasks not because they aren't smart enough, but because they suffer from a kind of digital amnesia and overconfidence as their work history grows.
Alex: So the paper is asking why AI agents struggle to stay on track during long projects — not a problem with raw intelligence, but something more like losing the thread?
Sam: That's a good way to put it. Most agents try to do everything in one long, continuous session. Imagine trying to build a complex piece of furniture from a massive manual while keeping every single tool, screw, and scrap of wood on your workbench at once. Eventually, the workbench gets so cluttered that you lose track of what you've already finished and start repeating work or making errors.
Alex: Like a messy desk leading to a messy project. So what's the fix?
Sam: The researchers propose a system that acts like a project manager. Instead of one long, messy session, they break the work into a repeating three-step cycle they call the "Manage-Execute-Audit" loop — or MEA loop for short. Think of it as a Project Manager, a Worker, and an Inspector all working together.
Alex: Walk me through how those three roles actually divide up the work.
Sam: Sure. First, the Manager defines a specific subtask — they call it a "contract" — with clear, concrete goals. Then the Worker performs only that one small step, in a fresh, clean environment with no leftover clutter from previous steps. Finally, an independent Auditor checks the work to see what actually changed, rather than just taking the Worker's word for it.
Alex: That last part seems important. The Worker doesn't get to grade its own homework?
Sam: Exactly, and that's the core insight. When an AI agent evaluates its own progress, it can convince itself that it completed a step even when it didn't — a kind of false confidence the researchers call "context rot." By handing that evaluation to an independent Auditor, the system forces the agent to prove its work rather than just claim it.
Alex: So the Auditor is essentially a fact-checker built into the process. Does that actually move the needle on performance?
Sam: The results suggest a significant improvement. In one benchmark, the success rate jumped from around 52% to 81% just by changing how the agent manages its tasks — not by using a more powerful model, but purely through this structural change. That's a meaningful finding, because it suggests that agent capability is often a system-level property. The scaffolding around the model matters as much as the model itself.
Alex: So you could take the same AI brain and get substantially better results just by organizing how it works?
Sam: That's what the paper argues. And it holds across different models and task types — the gains aren't specific to one particular AI system. The implication is that a lot of the reliability problems people attribute to weak models might actually be problems with weak organization.
Alex: If the system is running all this extra auditing on top of the normal work, does it become slow or expensive to run?
Sam: That's a reasonable concern, but the researchers found the opposite tends to be true. The Manager role is relatively lightweight. The Auditor does more work, yes — but the overall system often uses fewer total resources than the old approach. The reason is that unstructured agents frequently get stuck in loops, repeating failed steps over and over. By catching errors early and cleanly, the MEA loop actually cuts down on wasted effort.
Alex: So the overhead of auditing is less costly than the waste of spinning your wheels on mistakes you don't even know you've made.
Sam: Exactly. And there's a deeper point here. The system turns execution progress into a verifiable record — a series of confirmed facts — rather than a long, tangled transcript of actions that the agent has to interpret. That's a much more stable foundation for a long-running task.
Alex: It's almost like the difference between a project with clear milestones and sign-offs versus one where everyone just keeps working and hopes it comes together at the end.
Sam: That's a fair comparison. The researchers are essentially arguing that the discipline we apply to human project management — break it down, verify each step, don't move on until you're sure — is exactly what AI agents need too. The intelligence is still in the model. But the reliability comes from the structure around it.
Alex: That's a genuinely useful reframe — that improving AI performance isn't always about building a smarter system, but sometimes about building a better-organized one. Thanks for walking us through it, and thanks to everyone listening to ResearchPod.