arXiv:2610.41435v1 Announce Type: new Abstract: Given that AI agents can search the web broadly and deeply in real time, it is tempting to conclude that their outputs account for recent world events. We show that this conclusion does not hold in practice. While agents can search and easily find recent changes, the correctness of their responses depends on whether they search and what they search for. Popular agentic search benchmarks like BrowseComp cannot expose failures wherein agents do not recognize their own assumptions that should be verified, since these benchmarks explicitly state what needs to be found. In contrast, many user requests state only the final information need (e.g., an itinerary for a trip), leaving the agent to discover relevant changes (e.g., the temporary closure of a museum) and account for their consequences. To highlight such gaps, we introduce BlindToChange, a benchmark that measures whether agents proactively discover recent events that affect their responses. Our benchmark comprises requests for recommendations where an obvious candidate is no longer applicable due to a recent real-world event. These events are drawn automatically from Wikidata, allowing BlindToChange to be periodically refreshed. Strikingly, we find a big gap -- as high as 27.5 points, even at high reasoning effort -- in systems' performance, when the recent event is not explicitly mentioned compared to when we ask about it directly. Analyzing search trajectories, we learn that more than half of the failures can be attributed to the fact that agents do not directly search to verify whether a relevant fact has changed. Our benchmark highlights, and tracks, a new axis of progress, wherein systems account for recent information that is not explicitly mentioned in the user request.
BlindToChange: AI Agents Can Find Changes When Asked But Do They Look When Needed?
A new arXiv paper (2610.41435v1) introduces BlindToChange, a benchmark showing that AI agents score as much as 27.5 points lower when a recent real-world event affecting the answer is not explicitly named in the request than when they are asked about it directly, even at high reasoning effort. The authors, who draw the events automatically from Wikidata so the benchmark can be periodically refreshed, attribute more than half of the failures to agents not directly searching to verify whether a relevant fact has changed. The paper argues that popular agentic search benchmarks such as BrowseComp cannot expose these failures because they explicitly state what needs to be found, whereas many user requests state only the final information need.
Run your AI side-project on zahid.host
EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.