AIAny
Icon for item

OneDayAgent: Towards a Long-Horizon Harness for Autonomous Agents

Turns open-ended everyday requests into a managed long-horizon execution process that decomposes tasks into bounded subtasks, maintains compact execution memory under context pressure, and verifies and repairs final deliverables. Designed to run unchanged across multiple LLM backends and evaluated on AgentIF-OneDay.

Introduction

Most real-world personal and desktop requests span many heterogeneous steps, tools, and modalities, so a single uninterrupted agent loop quickly loses track of goals, state, and verification. OneDayAgent's core insight is to treat an open-ended request as a managed execution process: decompose work into bounded subtasks, keep only a compact, audited task state across rounds, and verify/repair the final deliverable before declaring success. This lets the harness tolerate different model behaviors and context limits while preserving correctness guarantees.

Key Findings
  • Managed MEA loop (Manage–Execute–Audit): each round the manager emits a bounded subtask contract, a fresh-context executor runs it, and an independent auditor inspects environment changes to update a compact, verifiable task state — so only audited facts persist across rounds.
  • Robust cross-backend generalization: the same harness runs without tuning across multiple LLM backends and execution backends, enabling consistent workflows even when models exhibit different execution styles.
  • Empirical gains on a long-horizon benchmark: when evaluated on AgentIF-OneDay across 104 tasks the harness achieves strong overall performance (reported top score 0.821 with a particular backend), demonstrating practical improvements on long, cross-environment tasks.
  • Practical tradeoff: discarding executor interaction history between rounds reduces state bloat and drift but requires reliable auditing; the harness focuses engineering effort on verification primitives and subtask contracts rather than monolithic context retention.
Who It's For and Tradeoffs

Great fit if you build or evaluate LLM-driven agents that must coordinate across tools, UIs, or terminals and need a repeatable, auditable execution pipeline. The harness is useful when model variability, context limits, or multi-step verification are primary failure modes. Look elsewhere if your tasks are short, single-step API calls or you prefer end-to-end learned controllers without explicit audited state — OneDayAgent trades end-to-end flexibility for modular correctness and auditability.

Information

  • Websitearxiv.org
  • AuthorsJingsheng Zheng, Xinyuan Fang, Jintian Zhang, Zhengke Gui, Huajun Chen, Ningyu Zhang
  • Published date2026/08/04

Categories

More Items

Benchmarks joint recovery of obfuscated platform messages and evidence-grounded web investigations by pairing 3,600 synthetic restoration inputs with 600 controlled web environments. Separately scores message-entry recovery and downstream web risk judgments, and provides a frozen multimodal evidence judge plus a resettable local sandbox for reproducible agent evaluation.

Measures how individual harness components—planning, action space, and context management—affect coding agents' success, cost, and behavior. Uses a modular harness across 176 matched settings on SWE-Bench Verified and Terminal-Bench 2.1 to isolate component effects and surface model- and budget-dependent trade-offs.

Finds token- and API-cost-saving harness mechanisms for long-horizon coding agents using automated recursive self-improvement; packages four surviving mechanisms (action fusion, context compaction, observation archiving, delegated reading) to cut recorded token traffic ~44.7–49.0% and API cost by about one third while preserving most capability.