Papers
Topics
Authors
Recent
Search
2000 character limit reached

Apodex 1.1: Scaling Agentic Intelligence for Complex Work

Published 24 Aug 2026 in cs.AI, cs.CL, and cs.LG | (2608.23283v2)

Abstract: General-purpose LLMs can reason and synthesize knowledge, but complex work also requires sustained interaction with files, information sources, and executable code, together with state maintenance, failure recovery, and verifiable delivery. We call this \emph{working capability}: sustained, verifiable progress toward a real-world objective. Apodex 1.1 develops this capability along two complementary dimensions. \emph{Environment Scaling} expands the diversity and verifiability of executable file, search, and code environments, while \emph{Agentic Coordination Scaling} trains agents to decompose long-horizon tasks, delegate parallel work, integrate asynchronous results, and replan. A shared execution harness and AgentOS maintain task state and provenance across tools and agents, and training turns environment trajectories and coordination traces into reliable behavior. Across complex professional work, finance, scientific research, mathematics, coding, and search, Apodex 1.1 reaches the leading performance band despite using a substantially smaller model than many frontier systems. The 35B-parameter Apodex 1.1 Mini further retains strong working capability in a locally deployable form. These results ground agentic intelligence in useful, verifiable work completed over time and advance our goal of building a \emph{Heavy-Duty Solver} for ambitious, long-running tasks.

Authors (76)

First 10 authors:

  1. B. An 
  2. B. Li 
  3. B. Wang 
  4. B. Zhang 
  5. B. L. Wang 
  6. C. Feng 
  7. C. Wei 
  8. C. Xue 
  9. C. Zhang 
  10. D. Ng 

Summary

  • The paper establishes Apodex 1.1, which frames agentic intelligence as a system for sustained, verifiable execution across complex tasks involving files, code, and data, rather than isolated answer quality. Key features include demand for working capability, execution harness, and AgentOS.
  • The methodology of Apodex 1.1 includes unified Supervised Fine-Tuning (unified SFT), reinforcement learning (agentic RL), and execution harnesses like AgentOS, improving coordination and task completion in multi-agent environments.
  • Apodex 1.1 demonstrated significant improvements in various domains, including professional work, finance, and scientific research, with notable gains in APEX-Agents, GDPVal, and FrontierScience-Research benchmarks, showing a win rate of 78.8 in GDPVal with the Agent Team setup and significant reductions in low-credit and zero-credit tasks on FrontierResearchBench.

Apodex 1.1 frames agentic intelligence as a systems capability rather than as an extension of answer quality. Its central construct, working capability, is the ability to make useful, sustained, and verifiable progress toward an objective while operating over files, evidence sources, executable code, persistent state, failures, and delivery constraints. The paper’s thesis is that complex work requires more than stronger reasoning: it requires an integrated policy and runtime capable of maintaining state, revising plans, recovering from failed actions, coordinating parallel work, and producing artifacts whose correctness and provenance can be inspected (2608.23283).

Problem formulation and central contributions

The paper treats completed work, rather than an isolated response, as the fundamental unit of evaluation. A task is specified by an initial workspace, objective, action space, transition and observation functions, resource budgets, delivery contract, and task-level verifier. This formulation distinguishes a natural-language request from the operational objective and acceptance criteria that govern execution. Success is consequently not identified with a plausible final answer. It depends on the terminal workspace, execution trace, artifact relationships, and contract-specific verification.

This perspective addresses a persistent weakness in existing agent evaluations. A model may know the correct method yet fail because it cannot identify the authoritative file, preserve consistency across intermediate artifacts, recover from a tool error, reconcile contradictory evidence, or determine whether its final output satisfies the requested interface. Apodex 1.1 therefore combines model training, environment construction, coordination mechanisms, and execution infrastructure within one stack.

The paper identifies two scaling dimensions:

  • Environment Scaling expands the diversity, fidelity, structural depth, and verifiability of executable file, search, and code environments.
  • Agentic Coordination Scaling expands the amount of useful work that can be decomposed, delegated, integrated, verified, and replanned across agents and time.

These dimensions are connected by a shared execution harness and AgentOS, which maintain workspace state, artifacts, provenance, branch state, asynchronous events, and delivery controls. Unified SFT and agentic RL then train the model on executable trajectories and coordination traces rather than on detached answers alone.

Environment scaling

Environment Scaling is presented as a primary source of capability growth, distinct from parameter scaling and inference-time compute. The relevant object is not a larger prompt collection but a broader distribution of executable task contracts with valid state transitions, realistic failure modes, resource constraints, and independently checkable outcomes.

File, search, and code worlds

File environments model professional work in which information is distributed across nested directories, heterogeneous formats, historical versions, and cross-file dependencies. The model must identify authoritative sources, reconstruct derivation chains, transform content, and deliver a coherent artifact. The paper reports a scenario registry spanning 33 domains, 318 occupations, and 1,208 deliverable clusters, with additional task variation at the level of task-specific angles. Difficulty is controlled through authority ambiguity, dependency depth, historical state, and business-logic structure rather than by simply increasing file count.

Search environments treat research as a sequence of discovery, acquisition, source triage, evidence alignment, reconciliation, and stopping decisions. Their gold objects include not only the final answer but also the relevant source set and claim-to-evidence relationships. This design is consistent with the broader movement toward execution-grounded information-seeking agents, including Search-R1 (Jin et al., 12 Mar 2025), WebThinker (Li et al., 30 Apr 2025), and DeepResearcher (Zheng et al., 4 Apr 2025).

Code environments provide stateful repositories and sandboxes in which agents modify files, execute commands, inspect failures, and satisfy executable tests. The paper emphasizes verifier hardening, isolation, and reward-hacking tests. Harvested tasks require fail-to-pass and pass-to-pass test consistency; synthesized tasks must additionally be probed for solutions that obtain reward without completing the intended change. This approach extends the environment-grounded logic established by SWE-bench (Christensen, 2024) and SWE-agent (Yang et al., 2024) to the broader Apodex file–search–code interface.

The three environment families are composable. Search results can become inputs to code, code can transform authoritative files, and final artifacts can be checked against both evidence and executable outputs. This compositionality is an important distinction from systems that treat search, coding, and document production as independent modes.

Verification and replay

The paper makes a strong methodological claim: generated tasks, reference solutions, and graders cannot be assumed mutually correct merely because they agree. Verification must be anchored in independent derivation, execution, provenance, or bounded semantic review. Each rollout therefore receives an immutable world manifest and an isolated mutable sandbox. Retained trajectories include generator versions, seeds, tool versions, action–observation sequences, file deltas, verifier versions, and termination reasons.

The “forward cheap, inverse expensive” construction principle summarizes the proposed data-generation regime. A latent state or reference program can cheaply generate and solve an environment, while the agent must recover the relevant solution path from the rendered workspace under interaction and delivery constraints. The approach permits large-scale synthesis while preserving explicit assurance boundaries, although the quality of the resulting distribution remains dependent on the fidelity and independence of the generators and verifiers.

Agentic coordination and AgentOS

Apodex 1.1 retains the lead-agent and dynamically spawned-subagent architecture of Apodex 1.0, but makes coordination state explicit through a persistent task board. Board entries contain bounded objectives, dependencies, ownership, returned evidence or artifacts, and resolution state. This changes delegation from a largely latent planning operation into an inspectable and mutable runtime object.

The task board enables several behaviors that are difficult to implement reliably through message history alone. A completed branch can unlock dependent work immediately; a failed premise can invalidate only its descendants; a slow branch need not block independent investigations; and new evidence can trigger targeted replanning. The coordinator is required to reconcile execution outcomes with the live plan rather than treating delegation as a one-shot preamble.

Asynchronous intervention

Apodex 1.1 incorporates user intervention during execution. Clarifications, new files, priority changes, methodological constraints, budget changes, pause or cancellation commands, and revised hypotheses can enter through a run-scoped control channel. Interventions that preserve the objective and delivery contract update the active task state while retaining causally valid work. Material changes create a new task contract, potentially reusing valid workspace state.

This mechanism addresses an important failure mode of front-loaded clarification: the information required to specify the correct plan may become available only after evidence has been inspected or intermediate computations have been completed. The paper nevertheless notes that intervention handling is a learned policy behavior, not merely an infrastructure feature; the system must determine which dependencies remain valid and which descendants require recomputation.

Asymmetric verification

The paper explicitly rejects unrestricted “solve the problem again” verification as a default. A verifier that receives the generator’s full context may be anchored by the same assumptions, while an equally unconstrained independent solution can introduce a second set of errors. Apodex instead assigns narrow verification tasks: attack a particular claim, inspect its evidence, search for counterexamples, verify atomic facts, test a computation, or check delivery compliance.

This asymmetry makes verification more actionable. A failed check identifies a specific claim, dependency, or contract clause that can be reopened on the task board. The mechanism operationalizes the targeted-verification principle developed in Chain-of-Verification (Dhuliawala et al., 2023), while embedding it in a persistent multi-agent execution state.

Adaptive effort and evidence-grounded synthesis

Agent Team does not use a fixed number of agents or uniform sampling. Additional effort is allocated to weak, contested, or load-bearing claims. Branches may pursue different hypotheses, methods, source classes, or query framings. Returned results are integrated asynchronously, and obsolete branches can be terminated.

Final synthesis is separated from lead-agent execution. An evidence-graph stage reconciles branch reports, retrieved sources, artifacts, and verifier findings into claims marked as corroborated, disputed, rejected, or unresolved. A writer then produces the final deliverable from this graph. Unsupported claims are qualified or omitted, while missing load-bearing dependencies trigger additional work rather than being filled by fluent prose. This design is closely related to evidence-assembly approaches such as Argus (Zhang et al., 15 May 2026), but is presented here as part of the same runtime rather than as an independent post-processing service.

AgentOS runtime

AgentOS instantiates the workspace as file state, retrieved evidence, executable state and logs, artifact index, provenance graph, and optional control state. It provides explicit filesystem namespaces for inputs, workspace artifacts, and outputs; optional read-only access to durable document libraries; backend-dependent private or shared workspaces; and capability-scoped file and shell access.

Several mechanisms target specific long-horizon failure modes:

Failure mode AgentOS mechanism
Plan loss during context compaction External task board with periodic reinjection
Race conditions in asynchronous work Message queues, interruptible waits, and delivery acknowledgements
Destructive cancellation near timeout Soft deadlines, bounded finalization, and hard outer timeouts
Undeclared or stale outputs Single-publisher lease, exact manifest, and baseline reconciliation
Ambiguous artifact ownership Explicit input, workspace, and output namespaces
Context overflow Provider-reported triggering, observation eviction, and conditional summarization

The artifact-delivery controls are particularly consequential. Ordinary execution writes to workspace storage, whereas publication requires an exact output manifest and a lease granting commit authority to at most one active session. At termination, files are reconciled against a baseline snapshot so that stale or empty files cannot satisfy the delivery contract.

The paper plainly concedes that AgentOS is not a transactional distributed runtime. Coordination state and filesystem state are not atomically checkpointed, process-restart recovery is outside the current contract, and historical filesystem rewind is unavailable. Thus, the runtime improves operational continuity but does not provide complete durable reproducibility under worker failure.

Training and credit assignment

Training begins with a unified SFT mixture covering general reasoning, search, file operations, coding, mathematics, scientific and financial analysis, professional delivery, recovery, and multi-agent coordination. The paper uses behavioral validity filters to remove invalid tool interactions, inconsistent states, ignored observations, and incomplete deliveries. Model-soup merging combines specialized SFT variants into a unified checkpoint.

Agentic RL then optimizes behavior over executable environment trajectories and coordination traces. Its central optimization technique, PIVOT-RL, localizes learning around consequential decisions identified retrospectively in failed or inefficient trajectories. Useful prefixes are retained, while corrective continuations are constructed from failure-relevant states with directional hints that are removed at inference time. This procedure targets tool misuse, insufficient evidence, uncorrected assumptions, and unproductive planning without requiring all credit to be inferred from a terminal reward.

Asynchronous optimization allows completed trajectories to enter training without waiting for slower episodes. This is operationally appropriate for heterogeneous file, search, code, and multi-agent workloads, although the paper does not provide a component-isolated ablation that would quantify the independent contribution of PIVOT-RL, asynchronous optimization, environment construction, or coordination training.

The reported RL curves show consistent improvement as RL compute increases on held-out search, knowledge, and science evaluations. The result supports the claim that executable trajectories provide a useful post-training substrate, but the evidence remains primarily aggregate: the paper does not establish whether gains arise from improved planning, tool selection, recovery, verification, or a change in task-specific priors.

Empirical results

Apodex 1.1 is evaluated in ReAct and Agent Team modes. ReAct is intended to expose the underlying policy with minimal orchestration, whereas Agent Team measures the additional value of learned decomposition, delegation, integration, verification, and adaptive computation.

The strongest reported gains are summarized below.

Evaluation Apodex 1.0 Apodex 1.1 ReAct Apodex 1.1 Agent Team
APEX-Agents 16.5 34.4 38.5
GDPVal 59.3 69.5 78.8
FrontierFinance 40.3 48.7 54.3
FrontierScience-Research 28.3 55.0 63.3
BioMysteryBench 17.6 23.5 35.3
Humanity’s Last Exam 49.0 53.2 56.1
DeepSearchQA 84.6 88.2 92.4

The generational improvement under ReAct is substantial. APEX-Agents rises from 16.5 to 34.4, more than doubling the Apodex 1.0 score, while FrontierScience-Research increases from 28.3 to 55.0. Agent Team adds a further 4.1 points on APEX-Agents, 9.3 points on GDPVal, 5.6 points on FrontierFinance, and 8.3 points on FrontierScience-Research. The implication is that the version improvement is not reducible to runtime delegation: the underlying policy improves materially even under the simpler scaffold, while coordination adds a further system-level gain.

Professional work and finance

On GDPVal, Apodex 1.1 reaches a 78.8 win rate with Agent Team and 69.5 with ReAct. On APEX-Agents, it reaches 38.5 with Agent Team and 34.4 with ReAct. The benchmarks differ in emphasis: GDPVal evaluates the quality of professional artifacts across 44 occupations, whereas APEX-Agents evaluates extended cross-application workflows. The joint result supports the paper’s claim that Apodex improves both artifact quality and sustained execution.

FrontierFinance shows a score of 54.3 with Agent Team, compared with 48.7 under ReAct and 40.3 for Apodex 1.0. The paper attributes the gain to coordinated evidence gathering, quantitative analysis, financial modeling, and verification. However, the Agent Team result does not include a separately reported YC-Bench comparison; the finance evidence is therefore strongest for FrontierFinance rather than for long-term business simulation.

Scientific research

Apodex 1.1 reaches 63.3% on FrontierScience-Research with Agent Team, compared with 55.0% under ReAct and 28.3% for Apodex 1.0. On BioMysteryBench’s Human-difficult Set, Agent Team obtains 35.3%, or 6 of 17 tasks, while ReAct obtains 23.5%, or 4 of 17. The gain is consistent with the proposed use of parallel evidence gathering and verification.

The results are weaker on the paper’s internal end-to-end FrontierResearchBench. Apodex 1.1 with Agent Team achieves a 12.4% full-task pass rate, while GPT-5.6-Sol and Grok-4.6 each reach 20.6%. This benchmark requires every specified research artifact, numerical result, executable output, and cross-artifact consistency check to pass. The low absolute pass rates demonstrate that end-to-end scientific delivery remains substantially harder than scientific question answering or rubric-based research responses. The paper appropriately treats this result as a limitation rather than presenting the broader scientific scores as evidence of reliable autonomous research completion.

Reasoning, search, mathematics, and coding

Agent Team reaches 56.1 on Humanity’s Last Exam and 92.4 F1 on DeepSearchQA, compared with 53.2 and 88.2 under ReAct. On the internal FrontierSearchBench, Agent Team reaches 69.1, exceeding the strongest listed comparison score of 67.4. It also reduces zero-credit tasks from 19.5% under ReAct to 9.8%, while the negative-score fraction falls from 4.9% to 2.4%. Because incorrect assertions are penalized, this pattern indicates improved completeness without a corresponding increase in unsupported guessing.

The mathematics results are among the paper’s strongest claims. On MathArena-derived competition sets, Agent Team obtains 36.5 on IMO 2025, 30.5 on IMO 2026, and 26.5 on USAMO 2026, exceeding the stated reference thresholds of 35, 29, and 25. Relative to Apodex 1.0 Agent Team, the gains are 24.0, 17.5, and 20.7 points, respectively. On IMO-ProofBench, Agent Team reaches 96.7% on Basic and 63.3% on Advanced. These results support the claim that the same coordination stack can improve search-free formal reasoning, although the paper does not show whether the mathematical gain derives from actual multi-agent decomposition or from other post-training changes.

Coding performance is competitive but not leading. Apodex 1.1 scores 70.8 on Terminal-Bench 2.1 and 77.7 on SWE-bench Verified, below the listed best scores of 91.9 and 92.2. This contradicts any broad interpretation that Apodex uniformly dominates across all complex-work domains. Its strongest relative advantages are in finance, structured search, scientific reasoning, and professional delivery rather than terminal software engineering.

Model-scale efficiency

The 35B-parameter Apodex 1.1 Mini provides an important efficiency result. With ReAct, it scores 40.0 on FrontierFinance, 45.0 on FrontierScience-Research, and 24.2 on APEX-Agents. Agent Team raises these to 50.2, 51.7, and 27.7, corresponding to gains of 10.2, 6.7, and 3.5 points.

The Mini result is not merely a smaller version of the main system. It shows that coordination and executable-environment training can produce large improvements at compact model scale. The paper therefore argues for a model-scale efficiency effect: organized inference and working-policy training partially substitute for parameter count on selected complex-work evaluations.

This claim must be interpreted cautiously. Several proprietary comparison models lack public parameter counts, and Agent Team changes inference compute, orchestration, and the number of active agents. The evidence establishes performance-band efficiency, not a controlled compute-normalized comparison against frontier systems.

HDS6 process evaluation

Outcome metrics do not establish whether a result was produced through a coherent or defensible process. HDS6 addresses this gap with six capability groups:

  1. long-horizon state coherence;
  2. evidence fidelity;
  3. hypothesis management;
  4. boundary and failure reasoning;
  5. tool use and execution-state management;
  6. self-correction under verification.

Each group contains four rubric items, for 24 scored items in total. A separate integrity gate zeroes the entire trajectory if the system fabricates a tool result or claims an action that did not occur.

Figure 1

Figure 1: HDS6 capability taxonomy and process-grading pipeline, with six four-item capability groups and an independent integrity gate.

The judging pipeline stitches tool calls, subagent dispatches, and intermediate observations into an ordered trajectory. Role-specialized mapping, judging, review, and arbitration assign each item a score of 0, 1, or 2 supported by citations to visible execution events. Private reasoning is excluded, and cited events are re-grounded against the recorded log.

The paper reports that the largest individual improvements are +1.3 for Initial Decomposition and +0.8 for Final Verification. These changes align with the explicit task board and asymmetric verification mechanisms. Evidence fidelity and hypothesis management also improve. However, HDS6 does not isolate the causal contributions of the model, training procedure, coordination strategy, environment distribution, or AgentOS. It is a process-localization instrument, not a component ablation.

Figure 2

Figure 2: HDS6 comparisons between Apodex 1.0 and 1.1 across Deep Discover, Deep Solve, and Deep Research settings.

The HDS6 comparison has a serious comparability constraint. Deep Discover compares an Apodex 1.0 397B Agent Team result aggregated over eight runs with a single Apodex 1.1 run. Deep Solve uses 397B ReAct, while Deep Research uses the 35B model with ReAct. The panels consequently differ in model scale, task family, execution mode, and aggregation protocol. The paper correctly limits interpretation to within-panel comparisons and does not present the figure as a matched causal ablation.

End-to-end cases

The case studies make the paper’s definition of working capability concrete.

In the molecular-dynamics case, the system produces a 22-file package for a three-copy Martini 3 protein system. The final system contains 63,484 particles, and steepest-descent minimization converges in 255 steps with a maximum force of 9.029×1029.029 \times 10^2 kJ/mol/nm. A binary verification establishes that the coordinates embedded in the submitted minimization input match the input structure for all particles with maximum absolute difference 0. The case demonstrates artifact integrity, repair, and cross-file consistency.

It also exposes residual defects. The coarse-grained model differs from the input residue sequence at 131 positions, and numbering restarts within three chains. These defects are disclosed rather than silently corrected because the execution constraints prohibited modifying the affected files. The case therefore supports the paper’s argument that a reliable agent must report unresolved defects instead of converting successful packaging into an unconditional scientific claim.

The fluorescence-imaging case is especially informative because two reasonable measurement definitions produce opposite conclusions. A per-mask mean yields a Welch PP value of 0.78 and no apparent group difference. A shared-ROI field mean yields a 2.4-fold difference, Cohen’s d=2.84d = 2.84, and P=0.0574P = 0.0574. Arbitration rejects the first definition because it discards signal-abundance information and is unstable under the intensity threshold. The final estimate is a control mean of 113.80 and experimental mean of 47.64, with Welch P=0.0593P = 0.0593 and Mann–Whitney P=0.10P = 0.10.

The result is a strong but statistically borderline effect. The paper correctly reports “not significant” at α=0.05\alpha = 0.05, notes that it would cross at α=0.1\alpha = 0.1, and avoids converting a large effect size into a definitive biological conclusion. With only three samples per group, the case primarily demonstrates measurement-definition arbitration and reproducibility analysis rather than inferential robustness.

The WGCNA case processes 6,000 genes and 50 samples, retaining 5,983 genes after CPM filtering and 5,000 by variance selection. All samples are retained. A signed bicor network at power 20 produces ten modules, but no tested power reaches the preset scale-free fit threshold of R20.85R^2 \geq 0.85; the selected power is therefore an explicit fallback at R2=0.8486R^2 = 0.8486. The strongest module–trait associations range from PP0 to PP1, all with FDR below PP2.

These associations are not causal claims. The paper notes that batch information was unavailable, the sample size limits covariate modeling, and module partitions depend on filtering, power, gene count, and merging parameters. It also warns that the hub-gene screen uses absolute GS, so candidate genes may have GS signs opposing the module eigengene. Most importantly, the delivered analysis.R was not executed end to end because R was unavailable. Numerical results came from an equivalent implementation, leaving a residual risk of version- or package-specific divergence.

Limitations and open questions

The empirical comparisons combine model changes, training changes, runtime mechanisms, inference budgets, and harness differences. ReAct versus Agent Team is informative about system-level benefit but does not isolate the marginal effects of delegation, adaptive effort, asymmetric verification, evidence-graph synthesis, or persistent task state. The paper similarly does not report systematic cost, latency, token, or energy tradeoffs for the coordination gains.

Several benchmark comparisons rely on reproduced external results or different agent scaffolds. The internal FrontierResearchBench result remains well below the best listed systems, and the coding results are also behind leading references. The paper’s claims are therefore domain-dependent rather than uniformly dominant.

The task-construction methodology introduces another open question. Independent verification reduces obvious grader failures, but synthesized environments may still encode distributions, failure modes, or authority structures that differ from real professional workflows. The report does not provide a comprehensive contamination analysis or a human-reviewed estimate of how representative its environment distribution is across the 33 domains and 318 occupations.

Finally, AgentOS lacks atomic joint checkpointing of filesystem and coordination state. This limits recovery after process failure and prevents historical rewind. The paper identifies joint versioning of task-board state, messages, artifacts, and workspace as an unresolved systems question. A further methodological question is whether HDS6 process scores predict external expert judgments of scientific or professional reliability better than terminal outcome metrics alone.

Conclusion

Apodex 1.1 presents agentic intelligence as sustained, verifiable execution over changing state. Its main contribution is the integration of executable environments, adaptive multi-agent coordination, persistent runtime state, artifact and provenance controls, and trajectory-based training into a single general-purpose stack (2608.23283). The reported gains are substantial in professional work, finance, scientific reasoning, structured search, and mathematical reasoning, and the 35B Mini demonstrates meaningful model-scale efficiency.

The evidence is strongest for the claim that coordinated execution improves complex-work outcomes relative to a simple ReAct scaffold. It is weaker for attributing gains to any individual system component, and the low full-pass rate on end-to-end scientific workflows shows that reliable artifact-complete research execution remains unresolved. The paper’s most consequential result is therefore methodological: it establishes completed, inspectable work as a more demanding and informative target than isolated answer accuracy, while making the remaining failures visible at the level of state, evidence, computation, and delivery.

Paper to Video (Beta)

No one has generated a video about this paper yet.

Whiteboard

No one has generated a whiteboard explanation for this paper yet.

Explain it Like I'm 14

1. Paper overview

This paper introduces Apodex 1.1, an artificial intelligence system designed to complete difficult, long-lasting tasks—not just answer a single question.

Many AI models can explain ideas or solve small problems. However, real work often requires many connected steps. For example, an AI might need to:

  • search for information,
  • read several files,
  • write and test computer code,
  • remember what it has already done,
  • fix mistakes,
  • work on several parts of a task at once, and
  • produce a final result that can be checked.

The paper calls this ability working capability. Apodex 1.1 is designed to improve this ability by giving AI better working environments and teaching multiple AI agents to coordinate their efforts.

2. Main objectives and research questions

The researchers are mainly asking:

How can an AI system become better at completing complicated real-world work over many steps?

They focus on several related questions:

  1. How can AI use tools reliably? Can it work with files, internet searches, and computer programs instead of only writing text?
  2. How can AI remember and manage progress? Can it keep track of files, evidence, plans, and unfinished work during a long task?
  3. How can AI recover from mistakes? If a program fails or new information changes the situation, can the AI fix its plan without throwing away useful work?
  4. Can several AI agents work together effectively? Can one main agent divide a task into smaller pieces, send them to helper agents, and combine their results?
  5. Can the final work be checked? Can the system show where its information came from and prove that its answer or files are correct?

The larger goal is to create what the paper calls a “Heavy-Duty Solver”: an AI that can take responsibility for ambitious tasks that last a long time.

3. Research methods and approach

The paper describes a complete AI system rather than one simple experiment. Its approach has two major parts.

Environment Scaling

Environment Scaling means creating many different computer-based situations in which the AI can practice useful work.

An environment is like a practice world or school laboratory. It gives the AI:

  • a starting situation,
  • tools it can use,
  • rules about what its actions do,
  • limited time or computer resources, and
  • tests that check whether the job was completed correctly.

The paper focuses on three kinds of environments.

File environments

These contain documents, spreadsheets, images, folders, and earlier versions of files. The AI must figure out which information is reliable and use it to create a useful final document.

This is similar to receiving a messy desk full of papers and being asked to prepare an accurate report. The AI must find the newest and most trustworthy papers rather than simply using the first document it sees.

Search environments

These test whether the AI can research a topic. It must:

  • create useful search queries,
  • find reliable sources,
  • compare information from different sources,
  • connect claims to evidence, and
  • admit when sources disagree or the evidence is uncertain.

This is like writing a school research project where every important statement needs support from trustworthy sources.

Code environments

These place the AI inside a computer programming project. The AI changes code, runs it, examines errors, and checks whether tests pass.

This is similar to repairing a machine while having a set of tests that show whether the repair worked. The AI must not only write code that looks reasonable; it must run successfully.

Agentic Coordination Scaling

The second major idea is Agentic Coordination Scaling. This means improving how several AI agents organize their work.

A lead agent first studies the overall problem and creates a task board. The board lists:

  • smaller tasks,
  • which tasks depend on others,
  • which agents are working on them,
  • completed results, and
  • problems that still need attention.

Helper agents can then work on different parts at the same time. For example, one might search for scientific evidence, another might analyze a spreadsheet, and another might check the first agent’s claims.

When a helper agent finishes, the lead agent adds the result to the shared task board. It can then change the plan, start new tasks, or stop tasks that are no longer useful.

This is like a group project with a shared online checklist. Team members work independently, but everyone can see the current progress and update the plan.

Persistent execution and verification

Apodex uses a shared software system called AgentOS. It acts like a long-term workspace that remembers:

  • files and their changes,
  • search results,
  • computer code and its outputs,
  • which agent created each result,
  • links between pieces of evidence, and
  • the current task plan.

The system also records the history of actions. This history is called a trajectory or execution trace. It allows researchers to replay what happened and determine whether a failure was caused by the AI, the computer environment, or a faulty test.

The system uses verifiers, which are checks for completed work. These might include:

  • running code tests,
  • recalculating numbers,
  • checking whether sources support claims,
  • examining file contents, or
  • asking a human expert to review the result.

A special idea in the paper is asymmetric verification. Instead of asking a checker AI to repeat the entire task, the checker receives a specific claim and its evidence. It then tries to find a mistake or counterexample. This is similar to asking a student, “Is this particular calculation correct?” rather than asking them to redo an entire book report from the beginning.

Training process

The researchers use two main types of training:

  • Supervised fine-tuning (SFT): the AI studies examples of good behavior, such as using tools correctly or organizing a task.
  • Agentic reinforcement learning (RL): the AI tries tasks in environments and receives feedback based on whether it makes useful progress and completes the job.

The researchers also study failures from real tasks and benchmarks. They turn common failures into new practice tasks, creating a repeating improvement cycle:

  1. observe where the AI fails,
  2. create tasks that practice those weaknesses,
  3. train the AI,
  4. test it again, and
  5. use the new failures to guide the next round.

4. Main findings and why they matter

According to the paper, Apodex 1.1 performs in the leading performance group across several areas, including:

  • professional and office work,
  • finance,
  • scientific research,
  • mathematics,
  • coding,
  • general reasoning, and
  • online search.

The paper also reports that Apodex reaches this level while using a smaller model than many other leading AI systems. This suggests that better training environments, memory, verification, and coordination may sometimes matter as much as simply making a model larger.

A smaller version, called Apodex 1.1 Mini, has 35 billion parameters. Parameters are the internal values an AI learns during training. They are somewhat like the adjustable connections in the AI’s “brain.” The Mini model is intended to be powerful enough for local deployment, meaning it may be possible to run it on an organization’s own computers rather than always using a large internet-based system.

The paper’s important message is that AI quality should not be judged only by whether it gives a good-looking answer. A better test is whether it can:

  • complete the requested work,
  • create usable files or other results,
  • use reliable evidence,
  • recover from errors,
  • keep track of its progress, and
  • explain or prove how it reached the result.

5. Implications and potential impact

If the results hold up under independent testing, Apodex 1.1 could make AI more useful for tasks that are too complicated for a single question-and-answer exchange.

Possible applications include:

  • preparing professional reports,
  • analyzing scientific data,
  • researching financial questions,
  • modifying and testing software,
  • organizing large collections of documents, and
  • supporting complicated investigations.

The use of several cooperating agents could also allow work to happen faster. While one agent researches, another could analyze data and a third could check the results.

However, the system also creates challenges. More agents and more tools can lead to more mistakes if their work is not carefully monitored. The system must therefore keep accurate records, protect important files, check evidence, and prevent agents from claiming success when they have not really completed the task.

In simple terms, the paper argues that the future of AI is not only about making models better at thinking. It is also about making them better at working: planning, using tools, cooperating, correcting mistakes, and delivering results that people can trust.

Knowledge Gaps

Knowledge gaps, limitations, and open questions

  • The paper does not provide a complete technical specification of the Apodex 1.1 model, including architecture, tokenizer, context length, training compute, data volume, parameter counts beyond the 35B Mini model, or inference configuration.
  • The training mixture is described conceptually, but its composition, provenance, filtering criteria, contamination controls, and proportions across SFT, agentic RL, environment trajectories, and coordination traces are not reported.
  • The paper does not quantify the contribution of Environment Scaling separately from model scaling, inference-time compute, tool access, or ordinary additional training data.
  • The claimed benefits of Agentic Coordination Scaling are not isolated through controlled ablations varying the number of agents, delegation policy, asynchronous execution, replanning, shared state, and verification while holding total compute constant.
  • There is no systematic comparison between Agent Team and simpler inference-time baselines such as independent parallel sampling, majority voting, sequential self-refinement, fixed-role multi-agent systems, or a single agent with an equivalent token and tool budget.
  • The paper does not define how “useful work,” “working capability,” “leading performance band,” or “Heavy-Duty Solver” are operationalized across tasks, making the headline claims difficult to reproduce or falsify.
  • The formal task contract introduces delivery verifiers, but the paper does not report the proportion of tasks with executable verifiers, human judgments, model-based reviews, or mixed evaluation procedures.
  • The reliability, validity, and inter-rater agreement of human review components are not quantified, particularly for professional work, scientific research, provenance fidelity, and artifact quality.
  • The paper does not establish that the proposed verifiers are independent of the generators, reference solutions, or training data strongly enough to rule out shared systematic errors and benchmark overfitting.
  • The effectiveness of verifier hardening and blind solver probes is asserted but not measured through documented attack rates, false-positive rates, false-negative rates, or before-and-after verifier audits.
  • Search-world evaluation does not resolve how source quality, web availability, paywalls, regional variation, page updates, and retrieval-index differences affect reproducibility.
  • The paper does not report whether search agents can distinguish authoritative sources from SEO-optimized, duplicated, adversarial, or AI-generated content under realistic web conditions.
  • The proposed claim-to-evidence alignment protocol remains underspecified: the paper does not define acceptable semantic entailment thresholds, treatment of contradictory sources, or procedures for evaluating uncertainty and citation completeness.
  • File-world coverage statistics—33 domains, 318 occupations, and 1,208 deliverable clusters—are not accompanied by task counts, sampling distributions, quality audits, or evidence that the generated tasks represent real professional workflows.
  • The paper does not test whether models trained on synthetic file worlds generalize to unseen organizations, document conventions, file formats, languages, or genuinely collected workplace artifacts.
  • Code-world results do not establish robustness to hidden tests, dependency conflicts, network restrictions, flaky tests, non-deterministic execution, security vulnerabilities, or repositories substantially different from the training distribution.
  • The paper does not quantify reward-hacking incidence in code, file, or search environments after the stated verifier defenses are applied.
  • The treatment of stochastic environments and replay does not clarify how nondeterministic tool outputs, external web changes, hardware variation, and timing-dependent failures are reproduced in practice.
  • AgentOS and the execution harness are described at a systems level, but their implementation details, overhead, failure modes, throughput, scheduling policy, and resource-isolation guarantees are not reported.
  • The paper does not provide a quantitative accounting of wall-clock latency, token consumption, tool calls, energy use, and monetary cost for ReAct and Agent Team executions.
  • It remains unclear whether Agent Team’s performance gains persist when systems are compared at equal total compute, equal latency, equal monetary cost, or equal number of environment interactions.
  • The adaptive Max Team Effort mechanism is not formally specified, and its stopping criteria, resource-allocation policy, and sensitivity to budget changes are not evaluated.
  • The paper does not analyze how coordination quality changes with team size, task-branch dependence, delayed results, failed subagents, duplicated work, or conflicting intermediate conclusions.
  • The task-board representation is proposed as a coordination mechanism, but there is no ablation showing whether explicit boards improve outcomes over hidden planning, natural-language scratchpads, structured workflow graphs, or external project-management representations.
  • The paper does not measure the frequency with which task-board state becomes stale, inconsistent, incorrectly updated, or misleading to the lead agent and subagents.
  • Asynchronous human intervention is described extensively, but the evaluation lacks quantitative results for intervention timing, intervention frequency, user burden, clarification quality, and preservation of valid prior work.
  • The distinction between task-preserving interventions and new task contracts may be difficult to apply in ambiguous cases; the paper does not specify or evaluate adjudication rules for borderline objective or acceptance changes.
  • The impact of user interventions on active subagents is not clarified, including how cancellation, notification latency, already-completed work, and inconsistent local states are handled.
  • The paper does not investigate adversarial or malicious user interventions, including attempts to corrupt provenance, bypass verification, introduce unsafe instructions, or redirect agents toward unauthorized actions.
  • The paper claims that narrow, asymmetric verification reduces context anchoring, but provides no controlled evidence comparing asymmetric verification with full-context review, independent end-to-end replication, or no verification.
  • The reliability of verifier agents under correlated model errors, misleading evidence, adversarial claims, and technically correct but incomplete artifacts remains unresolved.
  • The paper does not establish how provenance is represented, persisted, and validated across transformations involving derived files, copied content, code outputs, external sources, and multiple agents.
  • It is unclear how the system handles irreversible actions, destructive file operations, privacy-sensitive information, confidential documents, or tools with real-world side effects.
  • Safety, security, and privacy evaluations are largely absent, despite the system’s ability to search, execute code, modify files, delegate work, and maintain persistent state.
  • The paper does not report performance across languages, cultural contexts, accessibility requirements, or domains in which professional conventions differ substantially from the presumed training distribution.
  • Claims about the 35B Apodex 1.1 Mini being “locally deployable” are not supported with hardware requirements, throughput, memory usage, quantization effects, latency measurements, or capability degradation under constrained hardware.
  • The paper does not show whether the Mini model retains long-horizon reliability, recovery behavior, provenance fidelity, and coordination quality—not merely answer accuracy—when deployed locally.
  • Benchmark contamination and training-test overlap are not addressed for the reported finance, science, mathematics, coding, search, and professional-work evaluations.
  • The evaluation framework does not report confidence intervals, statistical significance, variance across random seeds, or the number of independent tasks and runs, limiting assessment of result stability.
  • The paper does not provide enough benchmark details, prompts, task contracts, environment manifests, trajectories, or verifier implementations to independently reproduce the reported results.
  • The relationship between benchmark performance and real-world productivity is not validated through longitudinal user studies, expert workflow comparisons, or measurements of downstream artifact adoption and correction effort.
  • The capability-development loop assumes that failures can be reliably classified into capability gaps, but the paper does not evaluate the accuracy, bias, or stability of this failure-attribution process.
  • The proposed acquisition-pressure coordinate ρacq\rho_{\mathrm{acq}} is explicitly non-universal, but its predictive validity, calibration across domains, and relationship to actual success probability are not empirically established.
  • The paper does not determine whether training on increasingly difficult executable environments improves broad generalization or instead produces narrow adaptation to the specific environment families and verifier structures.
  • The long-term effects of continual task-pipeline updates are unresolved, including catastrophic forgetting, capability interference, distribution drift, and feedback loops that over-prioritize easily measurable failures.
  • The paper does not compare the environmental and coordination approaches with non-agentic alternatives such as improved retrieval systems, workflow automation, domain-specific software, or human–AI collaboration at equivalent cost.
  • The manuscript appears incomplete: the provided text ends during the description of asymmetric verification, so the full evaluation methodology, results, limitations, and possibly safety analysis cannot be assessed from the supplied content.

Practical Applications

Immediate Applications

  • Long-horizon professional document production — legal, consulting, finance, and operations
    • Deploy Apodex-style agents to inspect heterogeneous workspaces, identify authoritative files, reconcile versions, perform calculations, and produce reports, spreadsheets, or presentations with source and artifact provenance.
    • A practical workflow would combine File environments, persistent workspace state, code-based calculations, and final contract checks for completeness and formatting.
    • Feasibility assumptions: Documents must be accessible in supported formats; organizational permissions and confidentiality controls must be in place; human review remains necessary for regulated or high-consequence deliverables.
  • Evidence-grounded research assistance — academia, intelligence, and policy analysis
    • Use the system to formulate search queries, triage candidate sources, follow references, reconcile conflicting evidence, and map individual claims to supporting sources.
    • Potential products include literature-review assistants, policy-brief generators, research dashboards, and citation-audit tools that expose source provenance and uncertainty rather than returning unsupported prose.
    • Dependencies: Reliable search and retrieval access, source-quality policies, protection against fabricated or inaccessible citations, and expert validation of contested interpretations.
  • Repository maintenance and software engineering
    • Apply the Code environment to issue resolution, test-driven patch generation, dependency inspection, debugging, refactoring, and regression testing.
    • An agent could operate in a sandboxed repository, execute tests, recover from failures, preserve state across attempts, and deliver a patch together with test results and an artifact lineage.
    • Dependencies: Isolated execution, trusted test suites, version-control integration, secrets management, and explicit limits on production changes. Passing tests alone may not establish security, maintainability, or correctness.
  • Automated quality assurance and verification
    • Use asymmetric verification agents to inspect specific consequential claims, calculations, code outputs, or deliverable clauses instead of asking a second agent to reproduce an entire solution.
    • This could support automated fact-checking, spreadsheet auditing, claim-to-source alignment, test review, and pre-publication quality gates.
    • Assumptions: Verification inputs must be sufficiently independent from the generator’s context; verifiers require access to authoritative evidence; human escalation is needed when automated checks disagree.
  • Internal knowledge-work automation
    • Organizations can build agents that manage multi-step workflows such as preparing meeting packs, comparing contracts, consolidating departmental updates, analyzing operational spreadsheets, or assembling due-diligence materials.
    • The task-board abstraction provides inspectable objectives, dependencies, assigned branches, completed work, and pending actions, making it more suitable for supervised enterprise workflows than an answer-only chatbot.
    • Dependencies: Integration with document repositories, databases, calendars, and communication systems; role-based access control; audit logging; and clear delivery contracts.
  • Interactive human-in-the-loop assistance
    • Users can clarify requirements, add files, change priorities, ask for progress, pause execution, or cancel branches while work is underway.
    • This supports workflows in which requirements emerge during execution—for example, revising a research question after reading an initial source or changing a report’s audience near completion.
    • Feasibility assumptions: The runtime must correctly distinguish a clarification from a material change in objective or acceptance criteria, preserve unaffected work, invalidate dependent work, and record interventions for auditability.
  • Locally deployed agentic assistance using the 35B Mini model
    • The reported local-deployment form could support organizations that cannot send sensitive documents to external APIs, including smaller firms, laboratories, universities, and public agencies.
    • Possible tools include an on-premise research assistant, private repository agent, local data-analysis assistant, or offline document-processing workflow.
    • Dependencies: Adequate local hardware, acceptable latency, secure sandboxing, model licensing, and independent evaluation on the organization’s own tasks. The paper’s performance claims do not by themselves establish reliability for every local deployment.
  • Agent-development infrastructure and evaluation
    • The execution harness, AgentOS, immutable world manifests, fresh sandboxes, replay records, verifier isolation, and task boards can be used immediately as infrastructure for building and testing other tool-using agents.
    • Research and engineering teams could create reproducible evaluations that measure not only answer correctness but also artifact completeness, provenance, recovery, intervention handling, time, and compute.
    • Dependencies: Task-specific verifiers must be trustworthy and resistant to reward hacking; tool versions, seeds, and environment states must be captured; privacy controls are required when replaying real user tasks.
  • Education and research training
    • Universities can use the framework to create practical assignments in which students or research assistants must gather evidence, manipulate files, execute analyses, document provenance, and submit verifiable artifacts.
    • Instructors could evaluate process quality—such as source alignment, reproducibility, and recovery from errors—in addition to final answers.
    • Assumptions: Educational deployments need transparent grading criteria, safeguards against outsourcing learning entirely to agents, and interfaces that reveal operational records without exposing sensitive internal reasoning.
  • Daily-life planning and administration
    • A constrained personal assistant could organize files, compare bills or insurance documents, prepare travel plans from multiple sources, maintain household spreadsheets, or track long-running application processes.
    • Persistent state and intervention handling are particularly relevant when a user adds new documents or changes constraints during execution.
    • Dependencies: Strong privacy protection, explicit user confirmation before external actions, safe handling of financial and identity information, and conservative behavior when sources conflict.

Long-Term Applications

  • Semi-autonomous scientific research systems
    • A mature system could coordinate literature discovery, experimental-data cleaning, code execution, hypothesis comparison, statistical analysis, and report generation across multiple research branches.
    • Agent Team’s decomposition, asynchronous result integration, replanning, and claim-level verification could form the basis of laboratory or computational research copilots.
    • Further development required: Domain-specific scientific verifiers, integration with laboratory instruments and databases, uncertainty calibration, reproducibility standards, and safeguards against invalid inference or unsupported novelty claims.
  • Financial analysis and investment research
    • Future systems could monitor filings and market data, reconcile financial statements, build models, test assumptions, and generate auditable research notes or risk analyses.
    • The paper’s emphasis on provenance, executable calculations, and recovery is well suited to workflows where a result must be traceable to data and assumptions.
    • Dependencies: Licensed and current data feeds, robust numerical validation, compliance with securities and fiduciary regulations, explainable decision records, and strict separation between analysis and unauthorized trading or advice.
  • Policy simulation and public-sector decision support
    • Government agencies could use coordinated agents to compare policy evidence, model implementation scenarios, identify conflicting assumptions, and prepare briefings with claim-level citations.
    • Persistent task state would allow analysts to incorporate new evidence or revised priorities without discarding valid prior work.
    • Further research required: Bias and representativeness audits, transparent provenance standards, stakeholder review, legal accountability, and methods for handling politically or scientifically contested evidence.
  • Autonomous software maintenance at organizational scale
    • Long-term systems could continuously triage issues, propose and test patches, update dependencies, migrate legacy code, and coordinate specialized agents across large repositories.
    • A shared task board could connect issue decomposition, implementation, security review, integration testing, and release preparation.
    • Dependencies: Stronger security verifiers, formal or property-based testing, safe rollback, human approval gates, supply-chain controls, and reliable understanding of undocumented system behavior.
  • Robotics and embodied automation
    • The task-contract and persistent-state framework could eventually support robots that coordinate perception, planning, tool use, manipulation, recovery, and human intervention over extended tasks.
    • Examples include warehouse operations, laboratory automation, inspection, maintenance, and multi-robot search.
    • Further development required: Real-time control, multimodal perception, physical-world safety guarantees, robust handling of stochastic transitions, latency-aware coordination, and sim-to-real validation. The paper itself primarily demonstrates file, search, and code environments, not physical robotics.
  • Industrial operations and engineering workflows
    • Future agents could coordinate maintenance records, sensor data, engineering drawings, simulations, work orders, and compliance documentation to diagnose failures or plan interventions.
    • Environment scaling could provide realistic digital twins or sandboxed operational environments, while provenance checks could link recommendations to measurements and calculations.
    • Dependencies: High-fidelity simulations, safe interfaces to operational technology, certification, cybersecurity, domain-expert oversight, and clear responsibility when recommendations affect physical assets.
  • Healthcare research and administrative support
    • Potential applications include literature synthesis, clinical-trial documentation, population-health analysis, medical coding support, and preparation of evidence summaries for clinicians or researchers.
    • Claim-level verification and explicit uncertainty could reduce—but not eliminate—the risk of unsupported medical statements.
    • Further development required: Validated clinical datasets, privacy-preserving deployment, medical-device and healthcare regulation compliance, prospective clinical evaluation, bias assessment, and mandatory professional sign-off. The findings do not justify autonomous diagnosis or treatment.
  • Energy-system planning and grid operations
    • A future agent team could combine weather forecasts, demand data, asset records, simulations, and regulatory constraints to evaluate maintenance or dispatch scenarios.
    • Code-based verification and persistent provenance could make scenario analyses more reproducible and auditable.
    • Dependencies: Real-time data quality, validated physical models, secure operational interfaces, reliability guarantees, and human control for decisions affecting grid stability.
  • Multi-agent organizational operating systems
    • AgentOS could evolve into a general runtime for delegating work among specialized agents, tracking dependencies, managing budgets, recording provenance, and routing human interventions.
    • Possible products include enterprise “work operating systems” for research, engineering, compliance, and project management rather than isolated conversational assistants.
    • Further development required: Standardized agent protocols, resource scheduling, identity and permission systems, cross-agent conflict resolution, cost control, observability, and benchmarks that measure useful coordinated work rather than the number of agent interactions.
  • Trustworthy autonomous knowledge work
    • The paper’s longer-term “Heavy-Duty Solver” vision could lead to systems entrusted with complete, long-running objectives: gathering evidence, executing analyses, producing artifacts, responding to changing requirements, and demonstrating why the result should be accepted.
    • This would represent a shift from chat-based assistance to verifiable delegation of complex work.
    • Major dependencies: Demonstrated reliability outside curated environments, robust generalization to unfamiliar tools and domains, calibrated uncertainty, secure autonomy, reproducible evaluation, legal accountability, and mechanisms to prevent plausible but incorrect completion from being mistaken for successful work.

Glossary

  • Acquisition pressure: A measure of how much candidate inspection and evidence navigation is required relative to the available tool-call budget. “as a first-order acquisition-pressure coordinate”
  • Agentic Coordination Scaling: Increasing an agent system’s ability to organize work across agents, branches, and time. “The second is Agentic Coordination Scaling”
  • Agentic RL: Reinforcement learning designed to improve decisions made by agents during extended, interactive tasks. “Agentic RL then improves long-horizon decisions”
  • AgentOS: A persistent runtime system that maintains state and supports tool, artifact, and agent execution. “AgentOS provides the persistent runtime beneath the harness”
  • Artifact lineage: The traceable chain connecting an artifact to the files, evidence, computations, and transformations that produced it. “Statement Review then checks consequential claims against sources, computations, and artifact lineage.”
  • Asynchronous intervention: User input or external interaction introduced while an agent is already executing a task. “Apodex 1.1 instead accepts a user message utu_t during execution”
  • Asymmetric verification: Verification in which a reviewer evaluates a narrowly specified claim or condition rather than reproducing the entire solution. “Apodex 1.1 constructs verification asymmetry: verification is deliberately narrower than generation.”
  • Authoritative state: The canonical, trusted version of the current workspace or task information. “preserving authoritative state across tools and agents”
  • Benchmark error: A failure or defect identified through evaluation tasks that can guide subsequent system development. “Real tasks, benchmark errors, and runtime failures are classified into capability gaps”
  • Branch state: The execution and dependency status of one line of work within a larger coordinated task. “maintains workspace, artifact, provenance, and branch state”
  • Capability gap: A deficiency in a model’s or agent system’s ability to perform a particular class of tasks. “Task Pipeline converts those gaps into new tasks”
  • Causal continuity: Preservation of valid relationships between earlier work, later decisions, and the evolving task state. “Training across these cases teaches the main agent to preserve causal continuity”
  • Claim-to-evidence alignment: The explicit association between a factual claim and the source material supporting it. “it includes the relevant source set, claim-to-evidence alignment”
  • Completion contract: A formal specification of what must be delivered and the criteria used to determine whether a task is complete. “defines observations and completion contracts”
  • Coordination trace: A recorded sequence of decisions and interactions among agents while organizing and executing work. “Agentic RL then improves long-horizon decisions over executable environment trajectories and coordination traces.”
  • Delivery contract: A task specification defining required outputs, constraints, and acceptance conditions. “the delivery contract DD states what must be delivered”
  • Dependency depth: The length or complexity of dependency chains that must be handled in a code environment. “including dependency depth, state-transition depth, test observability”
  • Exogenous state: Environmental state originating outside the agent’s chosen actions, such as controlled randomness or external conditions. “preserve the exogenous state, tool versions, and random seeds”
  • Executable environment: An interactive computational setting in which actions change state and produce machine-observable results. “An executable environment determines what states the model can observe”
  • Executable trajectory: A recorded sequence of actions, observations, and state changes produced through interaction with a runnable environment. “Diverse, faithful, and verifiable file, search, and code worlds expand the distribution of executable trajectories”
  • Evidence synthesis: The process of combining information from multiple sources into a supported conclusion. “Search environments model open-web research as discovery, acquisition, and evidence synthesis.”
  • Failure recovery: The ability to respond to unsuccessful actions while preserving valid prior progress. “recovering from failed actions”
  • Fidelity: The degree to which a simulated environment accurately represents the relevant structure and behavior of real-world tools or workflows. “Diversity without fidelity teaches behavior that fails in real tools”
  • Grader: An automated evaluator that determines whether a task solution satisfies specified requirements. “disagreements between a faithful solution and the grader”
  • Harness: A software layer that connects a model to environments, tools, state management, replay, and verification mechanisms. “The harness binds the model to File, Search, and Code environments”
  • Heavy-Duty Solver: The paper’s term for a system capable of undertaking ambitious, extended, and verifiable real-world tasks. “our goal of building a Heavy-Duty Solver”
  • Immutable world manifest: A fixed record describing the initial configuration and versions of an executable environment. “Each rollout receives an immutable world manifest”
  • Inference scaling: Increasing the computational effort devoted to solving an individual task at runtime. “inference scaling increases the computation spent on one task”
  • Interactive agent evaluation: Assessment of an agent through actions and responses within an evolving environment rather than through a single answer. “interactive agent evaluation has exposed this gap”
  • Long-horizon task: A task requiring many dependent actions, decisions, or interactions over an extended execution period. “The limiting capability is therefore not reasoning in isolation, but the ability to turn reasoning into sustained work inside a changing environment.”
  • Max Team Effort: A runtime mechanism for adapting the amount of parallel work performed by an agent team. “adaptive Max Team Effort”
  • Multi-agent coordination: Organization of work among multiple autonomous or semi-autonomous agents. “multi-agent coordination within one policy”
  • No-op transition: A state transition that performs no substantive modification, often used for read-only interaction. “A no-op transition permits read-only actions.”
  • Observation interface: The mechanism through which an agent receives information about the environment after taking an action. “Ω\Omega is the observation interface”
  • Open-web research: Research conducted over publicly accessible, heterogeneous online sources. “Search environments model open-web research as discovery, acquisition, and evidence synthesis.”
  • Provenance: A record of the origin, history, and transformations of data or artifacts. “maintains workspace, artifact, provenance, and branch state”
  • ReAct: An agentic prompting or execution paradigm that interleaves reasoning with actions and observations. “ReAct provides a lower-scaffold view of the model's working capability”
  • Replay: Re-execution of a recorded task using preserved environment and tool information to check reproducibility. “A trajectory is retained only when its initial state can be reconstructed, tool execution is isolated, and the verifier can be replayed.”
  • Replanning: Revising an existing task plan in response to new evidence, failures, or changed conditions. “delegate parallel work, integrate asynchronous results, and replan”
  • Reward hacking: Obtaining a high evaluation reward without genuinely completing the intended task. “We additionally test whether a solver can obtain reward without actually completing the task”
  • Sandbox: An isolated execution environment that restricts a program or agent from affecting protected systems. “Each rollout receives an immutable world manifest and a fresh mutable sandbox.”
  • Self-supervised tool-call learning: Learning to invoke tools from automatically derived training signals rather than manually annotated action labels. “Toolformer established self-supervised tool-call learning”
  • State-transition operator: A formal function describing how an action changes the environment or workspace state. “T\mathcal{T} is the state-transition operator”
  • Staged return: The practice of returning partial results from agents as soon as they become available, rather than waiting for all branches to finish. “staged returns, shared artifacts, lifecycle control, and verification hooks”
  • Sticky routing: Assigning all interactions from one session to the same execution worker. “Sticky routing keeps a session on one worker.”
  • Structured verdict: An evaluation result represented as organized checks or fields rather than a single unstructured judgment. “SDS_D may be a scalar score, a vector of checks, or a structured verdict.”
  • Task contract: A formal representation of a task, including its workspace, objective, actions, transitions, observations, budgets, delivery requirements, and verifier. “We use one task contract throughout this report”
  • Task Pipeline: A development process that converts observed capability deficiencies into new training or evaluation tasks. “Task Pipeline converts those gaps into new tasks”
  • Test observability: The degree to which a task’s tests expose whether the intended behavior has been achieved. “Code worlds require different calibration coordinates, including dependency depth, state-transition depth, test observability”
  • Trajectory: A time-ordered sequence of inputs, actions, observations, and state changes during task execution. “Let HH denote the realized trajectory horizon”
  • Trajectory horizon: The number of interaction steps or time points comprising an execution trajectory. “Let HH denote the realized trajectory horizon”
  • Typed observation: An environment response represented according to a defined semantic or data type, such as a tool result, failure, or status update. “the harness and AgentOS connect both dimensions through persistent execution state, typed observations”
  • Verifier hardening: Strengthening an evaluator so that it is resistant to incorrect solutions, exploits, or inconsistent test conditions. “As these transformations can invalidate an existing grader, verifier hardening precedes task perturbation”
  • Working capability: The ability to make useful, sustained, recoverable, and verifiable progress toward a real-world objective. “We call this working capability: sustained, verifiable progress toward a real-world objective.”

Open Problems

We haven't generated a list of open problems mentioned in this paper yet.

Tweets

Sign up for free to view the 6 tweets with 325 likes about this paper.