Cover image

The Assistant Remembered, but the Answer Ignored It

TL;DR for operators A memory-enabled assistant can correctly recall a group’s preferences and previous decisions yet produce a response that ignores them. In GroupAssistBench, Hu and colleagues evaluate this gap using 2,395 instances from real group conversations.1 Under a matched GPT-5.6-terra backbone, EverMemOS achieves higher factual recall than full context (0.621 versus 0.570), but markedly lower open-ended assistance scores (0.247 versus 0.431). ...

November 14, 2026 · 8 min · Zelina
Cover image

Keep the Record, Rebuild the Rule

TL;DR for operators An AI agent can retain a complete record of what it did without permanently storing every rule it infers from that record. This distinction matters when an instruction derived from one successful task is subsequently reused in circumstances where it no longer applies. A new agent-memory architecture called Anti-Persistence keeps execution trajectories and outcomes but generates task-specific guidance only when needed, discarding that guidance afterward. Across nine benchmark–model combinations, it achieves 59.9% mean held-out success, compared with 53.5% for trajectory-only memory, 49.0% for abstraction-only memory, and 49.3% for joint memory. ...

November 7, 2026 · 8 min · Zelina
Cover image

The Search Stack Changes the Answer

TL;DR for operators An AI research assistant’s accuracy cannot be reliably predicted by selecting the strongest language model, connecting a powerful search service, and adding specialized agents. Those components must work together. In HyperBrowseComp1, replacing native search with Exa improved GPT-5.6 Sol accuracy from 19.15% to 26.71%, while reducing Gemini 3.7 Flash accuracy from 31.68% to 22.22%. A separate multi-agent configuration completed only 330 of 423 attempts and answered 17.73% correctly overall. ...

October 27, 2026 · 8 min · Zelina
Cover image

Same Actions, Different Outcomes: The Cost of Tool-Schema Bias

TL;DR for operators Changing how an agent calls tools can change its task success even when the underlying operations remain identical. In a controlled study, one model’s success fell from 78.5% to zero after tools were consolidated into a particular interface representation, then recovered to 75.2% under another merged representation. Across nine main open-weight models, fully merging tools reduced success by a median of 19 percentage points. ...

October 23, 2026 · 9 min · Zelina
Cover image

The Agent Knows What to Click. Can It Find the Target?

TL;DR for operators An AI agent can identify the correct kind of dashboard action without reliably performing it. In DashAct, one model achieves 98.8% action-type accuracy but only 2.5% complete Action Success, even when supplied with the correct preceding interaction history and dashboard state. The benchmark evaluates 357 analytical tasks across 175 interactive dashboards. Its three diagnostic stages separate autonomous task execution, next-action prediction with verified context, and fine-grained target localization with explicit visual guidance. ...

October 22, 2026 · 9 min · Zelina
Cover image

When Old Instructions Outlive Their Authority

TL;DR for operators An AI agent can retain every instruction in a conversation and still execute the wrong task. The problem becomes acute when users replace requirements, withdraw constraints, or revise decisions on which earlier work depended. A controlled study introduces IntentFlux, a benchmark that measures this failure under changing user instructions.1 In a turn-matched experiment, mean task score falls from 0.734 without revisions to 0.469 with revisions. Additional conversation length alone cannot explain the difference. ...

October 22, 2026 · 8 min · Zelina
Cover image

The Planner Trusted the Wrong State: A New Security Boundary for Embodied Agents

TL;DR for operators An embodied agent can receive the correct user instruction and still plan toward the wrong objective if the internal description of its environment has been manipulated. Liu et al. test this failure mode by altering planner-visible state semantics rather than changing the instruction, model, planner, executor, or environment itself.1 ...

September 6, 2026 · 7 min · Zelina
Cover image

When Model Output Can Change State: An Architecture Guide to Agent Reliability

TL;DR for operators A tool-using agent does more than generate an answer. It observes part of a workflow, carries information forward, decides what to do, changes external state, and then reacts to the result. A wrong answer in a chatbot may remain text; a wrong action in an agent can alter a file, submit a transaction, call the wrong service, or create a bad state that later decisions treat as valid. ...

September 6, 2026 · 7 min · Zelina
Cover image

Audit the Step, Not the Aftershock

TL;DR for operators When an autonomous analysis agent makes one questionable operation, every later operation may inherit the damage. An audit that merely asks which steps look unusual can therefore produce a long queue of downstream symptoms rather than isolate where new violations occurred. Ahmed Hassoon and Mark Dredze formalize a different target: score each operation according to whether it behaved as expected given the state it actually received.1 Under their assumptions, a correctly executed downstream step remains statistically null even when its input was already corrupted. This makes one-step scoring useful for narrowing a review queue. ...

August 28, 2026 · 8 min · Zelina
Cover image

After the Bad Memory: Repairing the Decisions It Already Touched

TL;DR for operators When an agent discovers that a stored customer preference, prior observation, or workflow fact was wrong, deleting that record may be too late. The faulty information may already have shaped a plan, triggered a tool call, entered the final answer, or created new persistent memories. Yu et al. propose a repair mechanism that follows those dependencies rather than resetting everything.1 On their 150-case controlled benchmark, it recovered 85.3% of cases, compared with 77.3% for LLM-judge repair, while reducing the replay ratio from 21.7% to 12.3% and average LLM calls from 9.80 to 5.70. ...

August 21, 2026 · 7 min · Zelina