The daily field guide to agent engineering

Measure the pairing.
Preserve the authority.

Sunday evening’s research batch turns the spotlight on the harness: which model it fits, which decisions it can reuse, which evidence memory retrieves, and what a recovering agent is still allowed to do.

The 30-second take

Evaluate the model and harness together. Reuse resolved decisions, not unchecked assumptions. Let memory revise retrieval with evidence. After failure, separate permission to act from evidence of what happened.

Today’s reading list

Showing all 4 items

01
arXiv research · Sunday announcement batch · Submitted October 23

A good model can still be a bad pairing.

When Agents Fail separates task correctness from valid completion.

An agent benchmark measures a model–harness system, not the model alone.

The authors compare OpenCode, Codex CLI, Pi CLI and DeepAgents across four core models, with native references and stress conditions. Their 111 settings yield 52,168 trajectories across six benchmarks. Rankings vary by model and task; finishing normally with an evaluable result is not the same as solving the task correctly.

Evidence & limits. This is an author-reported preprint under review, not a universal harness leaderboard. Valid Completion Rate measures operational validity, not answer quality. Pairing-level observations do not isolate a single causal component; versions, budgets, benchmark panels and task mix matter.

For builders · Editorial analysis

Make model changes a regression event for the whole harness. Track correctness, normal completion and token load including failures separately. Promote the pairing that works on your tasks, not the winner of an unrelated aggregate.

02
arXiv research · Sunday announcement batch · Submitted October 23

Do not reason twice about a resolved action.

HarnessMM stores guarded continuations at the model–tool boundary.

A later tool receipt may confirm a decision already made, rather than require a fresh reasoning call.

Executable Decision Graphs retain exact actions, literal arguments, dependencies and guards. Observed receipts activate eligible continuations; new semantic decisions or unsupported evidence return to the original model. Actor weights stay fixed.

On the paper’s 98-task HumanEval test split, the Codex comparison preserves 90.82% success while reducing actor tokens by 29.54%.

Evidence & limits. Author-reported preprint results, not guaranteed savings for arbitrary workloads. Companion configurations and task-specific adapters affect comparisons. The main quality–cost result does not attribute every saved token to reuse alone. Model-call, cache/context accounting, configuration search and recovery costs must be distinguished. In an MBPP ablation, the no-graph condition solved four more tasks than full HarnessMM: savings are not universally quality-neutral.

For builders · Editorial analysis

Try guarded reuse where exact next actions are already resolved. Keep an explicit abstain path, and measure complete-task quality and cost rather than counting skipped calls as savings.

03
arXiv research · Sunday announcement batch · Submitted October 23

Let the graph challenge the first retrieval.

ActionRAG combines cautious indexing with query-local evidence refinement.

A similarity score is a starting point, not necessarily the final evidence ranking.

ActionRAG reconciles entity types and identities, retrieves entity and triple seeds, then uses bounded graph diffusion to refine evidence. Seed protection and hub penalties aim to recover relevant connections without letting popular nodes dominate. Across eight deterministic MemoryAgentBench columns, the authors report a 55.1 unweighted mean, 5.4 points above the strongest compared retrieval-based baseline.

Evidence & limits. Results come from the arXiv manuscript; independent replication was not checked. Baselines largely come from the benchmark paper, and LLM-judged tasks are excluded. Cost accounting excludes graph construction, storage and local embedding and uses November 2025 prices. Table 4 includes three query costs above $0.001 despite the abstract’s below-$0.001 wording. The 440.7 ms figure adds separately measured component p99s; it is not observed end-to-end p99 latency.

For builders · Editorial analysis

Test graph refinement against source-preserving retrieval with the same reader and budget. Measure ingestion and serving together, plus end-to-end latency and entity-resolution errors.

04
arXiv research · Sunday announcement batch · Submitted October 22

A checkpoint is not permission to retry.

Permission to Retry separates recovery state, current authority and external effects.

A lost acknowledgment does not prove that an action failed to happen.

The study executes 336 controlled histories across native LangGraph and Temporal hosts. Per host, retained-ledger reconciliation conforms in all 42 cases: 21 completions, 15 denials and six unresolved outcomes with reservations retained. Cached retry, permission revalidation and stable-key retry policies conform in 30, 36 and 31 cases respectively.

Evidence & limits. This preprint isolates application recovery policies, not LLM behavior or framework defaults. Paired host outcomes are identical. The finite schedules and provider contracts bound the result; “42 passes” includes correct denials and unresolved cases, not 42 successful actions. The separate InfinityOS component study uses repository fakes, not a production deployment evaluation. There are no real provider/model trials or public execution repository; released tables alone do not reproduce the experiment.

For builders & governance owners · Editorial analysis

Keep a durable effect ledger and explicit unresolved obligations. Check authority for a new dispatch separately from permission to reconcile an existing effect. Test revocation, lost receipts and ambiguous outcomes before approving automatic recovery.

How to read this edition

Sunday news can carry a Monday listing.

Coverage window: October 25, 00:00–23:59 EDT. These papers appear in the Monday October 26 arXiv listing. Under arXiv’s official schedule, the corresponding announcement occurs Sunday at 20:00 Eastern. That supports inclusion in this window; it does not turn the earlier submission timestamps into Sunday submission dates.

HarnessMM, When Agents Fail and ActionRAG were submitted October 23 UTC. Permission to Retry was submitted October 22 UTC after the Eastern cutoff. Announcement placement is inferred from the observed listing and published schedule, not an individually captured release timestamp.

Research results are author-reported, not independently reproduced here. No peer-review acceptance is inferred from arXiv availability. Different benchmarks, model versions, budgets and scoring rules prevent direct comparisons across cards. Diagrams explain mechanisms, not relative performance.

Source check

Research-rich, announcement-light.

arXiv listings, histories and full texts were checked live. AINews redirects to Latent Space; the latest visible October 24 issue covers October 22–23. No October 25 issue was visible during this run, and old newsletter leads were not relabeled as new.

No additional substantive October 25 governance-policy or sovereignty announcement was verified. The recovery study supplies a practical governance angle. We found no public completion result for AWS’s previously announced sovereignty exercise, so it is not repeated as a successful test. The sovereignty filter is retained even though no card qualifies today.

Four focused items, without padding to a quota. Builder recommendations are editorial analysis. Only public research and general content are included.

Browse Past Editions →

Previous editions

View all editions