Benchmark Radar™
RSS Contact Star —

Daily AI benchmark brief: 2026-10-23

630evidence observations
13sources represented
17public-attention signals

Daily briefing

  1. The new EpiSEM-Bench release tests whether tool-using language-model agents act unsafely when a tool returns statements that are true but omits a safety-relevant fact. Its 300 matched safe and unsafe task pairs across six domains vary the missing evidence rather than the user’s benign request, separating evidence-recovery behavior from ordinary refusal behavior. Why it matters: If you evaluate agents that can take consequential actions, this adds a failure mode that standard harmful-request tests miss: proceeding because the environment supplied incomplete information. It can change whether a safety suite tests only what an agent was told or also whether the agent notices what it still needs to know. Evidence: E014. High confidence.
  2. AgentPhishing is a new benchmark that evaluates whether adaptive, persuasive phishing messages can make language-model email agents both miss the attack and comply with its malicious request. It measures the agent’s response, not only whether it labels an email as phishing. Why it matters: If you are selecting an email agent that can access private information or act for users, detection accuracy alone does not establish safe behavior. This benchmark supports a separate deployment decision about whether the agent follows attacker instructions after its detector fails. Evidence: E002. High confidence.
  3. The new NASICON retrieval-augmented generation benchmark packages a 52-question materials-science suite with results from 12 generators and multiple judge models. Retrieval-augmented generation means answering with information fetched from an external collection. The release also includes re-scoring runs, reasoning-ablation repeats, timestamps, software versions, and audit trails. Why it matters: If you are comparing retrieval systems or automated graders, this artifact lets you inspect whether rankings depend on the answer model, judge model, or evaluation procedure. That can change a suite-selection decision when a single automated judge would otherwise be treated as ground truth. Evidence: E003. High confidence.
  4. The new MICA 2026 test release addresses training contamination in protein-model evaluation. It contains 30 cryogenic electron microscopy maps released in 2026, and every evaluated protein chain has no more than 25% sequence identity to any Protein Data Bank entry released before 2026. The creators also publish raw evaluation outputs and fixed-seed sampling details. Why it matters: If you evaluate systems that may have learned from historical protein structures, this split offers a clearer test of generalization to newly released and dissimilar proteins. It can change whether reported performance is interpreted as reconstruction of unfamiliar structures or possible recall of close training examples. Evidence: E012. High confidence.
  5. AgentVQA is a new offline benchmark for vision-language models—models that answer questions about images or video—covering web agents, robotics, first-person video, games, and spatial planning. It is explicitly positioned as a scalable complement to costly simulator and real-world evaluations, not as their replacement. Why it matters: If you are choosing a suite for early agent-model screening, AgentVQA offers one common offline comparison across five interactive domains. Its stated role also clarifies the decision boundary: it can reduce the candidates sent to expensive live tests, but the supplied description does not establish that offline scores predict deployed performance. Evidence: E001. Medium confidence.
  6. The new specification-oracle-gap study audits coding-agent benchmarks for requirements present in grading tests but absent from the natural-language task description, such as exact constant names, module paths, or message text. It reports a static audit spanning five programming languages and distinguishes task completion from reproducing unstated implementation details. Why it matters: If you use test-graded coding benchmarks to select an agent, this changes how a failed task can be interpreted. Some failures may measure access to hidden project conventions rather than the ability described by the prompt, so benchmark maintainers can use the audit to identify tasks needing clearer specifications or separate reporting. Evidence: E028. High confidence.

What arrived

What benchmarks, datasets, or evaluation methods did the radar first see today?

high confidenceNot enough evidence

The captured feed first observed a broad mix spanning agent behavior and safety, scientific vision, remote sensing, cybersecurity, education, and software engineering. Notable arrivals include AgentVQA, AgentPhishing, EpiSEM-Bench, DuoCook, WildDepth, CryoAtlas, LongRS-Bench, CellTrack-Bench, SecLog-Bench, and REGATTA. It also surfaced methods based on matched lifecycles, fault injection, specification audits, exact option-set grading, and structured rubric trees.

These arrivals test whether systems can understand agent situations, resist phishing, recover missing safety evidence, coordinate in games, process scientific images, reason over satellite changes, track cells, and interpret security logs. Several also change how evaluation is performed by injecting known faults, auditing hidden test requirements, or breaking complex reports into individually scored claims.

Takeaway: This is a selective overview of first observations in the captured keyword-filtered feed, not a complete inventory or evidence of field-wide novelty. The supplied packet covers only part of the first-observed registry, so the remaining artifact records would be needed for a comprehensive answer.

Another reading: First observed by this radar does not mean newly created or newly released worldwide. Some records were merely discovered today, while source outages and the packet’s partial selection could omit important artifacts or skew the apparent mix.

  • S024 artifacts first observed by the radar today: 315

Which of today's arrivals document how they score an answer?

high confidenceNot enough evidence

The clearest documented examples are IFC-MCQ, with exact option-set grading; TerrierTA, with rubric-based short-answer grading against an instructor reference and human graders; the AI Professions prompt benchmark, with criterion-level verdicts; HeriKGQA, with typed reference values and a scorer; TutorCaseBench, with source-grounded rubrics; NASICON, with multiple judges and rescoring records; and FrontierCS, with development and held-out evaluation suites.

These artifacts describe more than a question set. They indicate what counts as correct, such as matching an allowed option set, satisfying rubric criteria, agreeing with typed reference values, or passing a hidden test suite. The Decision Index also documents a weighted composite and rank-tie rule rather than reporting an unexplained leaderboard score.

Takeaway: These are the strongest scoring-method examples visible in the supplied evidence, but the packet does not establish that every method is fully reproducible. Full dataset cards, judge prompts, rubrics, reference answers, and scorer code would be needed to verify all arrivals comprehensively.

Another reading: A scoring description is not necessarily an auditable scorer. NASICON mentions judges and rescoring outputs without supplying the complete judging procedure in this packet, while FrontierCS deliberately keeps its final evaluator and held-out suite private. Those designs limit independent verification despite documenting the scoring structure.

  • S024 artifacts first observed by the radar today: 315

What is still moving

Which artifacts the radar already tracked moved measurably, and over what span?

medium confidenceNot enough evidence

The registry contains measurable download changes for the artifacts represented by the cited movement statistics, each measured cumulatively across its full tracked span rather than as a one-day change.

The statistics identify the artifacts, direction of download movement, and tracked windows. However, the packet provides no citable evidence records for those artifact-specific claims.

Takeaway: Use the cited statistics to render the artifact names, movement values, and spans, but treat the answer as incomplete until matching evidence records are supplied. This applies only to the captured keyword-filtered feed.

Another reading: The movement statistics themselves are structured and explicit, so they may be adequate for reporting. The stricter limitation is that no required artifact-level evidence IDs accompany them.

  • S027 downloads change for lmarena-ai/leaderboard-dataset: 142,702.0 downloads
  • S028 downloads change for RoboDojo-Benchmark/RoboDojo: 132,336.0 downloads
  • S029 downloads change for vedangfake/chess-slm-benchmark: 18,793.0 downloads
  • S030 downloads change for alexshpunt/explicit-edit-benchmark: 17,562.0 downloads
  • S031 downloads change for hf-benchmarks/transformers: 10,991.0 downloads
  • S032 downloads change for Rapidata/text-to-svg-human-feedback-benchmark: -7,580.0 downloads
  • S033 downloads change for RyeAI/danish-asr-leaderboard: 6,404.0 downloads
  • S034 downloads change for Agnuxo/P2PCLAW-Innovative-Benchmark: 5,992.0 downloads

Which of that movement is corroborated by more than one data source?

high confidence

None of the registered download movements is corroborated by more than one data source; every cited movement statistic is marked single-source.

Each reported download change came only from Hugging Face. Seeing an artifact elsewhere would not confirm the download change unless another source measured that same metric.

Takeaway: Treat all cited movement as uncorroborated platform-reported activity within this captured feed, not independently confirmed movement.

Another reading: Some tracked artifacts were sighted by multiple sources, but that does not establish that multiple sources measured the same movement metric.

  • S026 tracked artifacts today seen by more than one data source: 11
  • S027 downloads change for lmarena-ai/leaderboard-dataset: 142,702.0 downloads
  • S028 downloads change for RoboDojo-Benchmark/RoboDojo: 132,336.0 downloads
  • S029 downloads change for vedangfake/chess-slm-benchmark: 18,793.0 downloads
  • S030 downloads change for alexshpunt/explicit-edit-benchmark: 17,562.0 downloads
  • S031 downloads change for hf-benchmarks/transformers: 10,991.0 downloads
  • S032 downloads change for Rapidata/text-to-svg-human-feedback-benchmark: -7,580.0 downloads
  • S033 downloads change for RyeAI/danish-asr-leaderboard: 6,404.0 downloads
  • S034 downloads change for Agnuxo/P2PCLAW-Innovative-Benchmark: 5,992.0 downloads

What it means

What should someone building or evaluating AI systems do differently today?

medium confidence

Within this captured feed, review newly released safety and agent tests rather than immediately changing production gates: dataset, evaluation, and benchmark observations rose in the recent window versus the prior window, but category composition showed no material shift.

Try the new AgentPhishing and EpiSEM-Bench releases against relevant email or tool-using systems, and consider AgentVQA where visual agent scenarios match the product. Treat them as candidate tests, not validated standards.

Takeaway: Expand staging evaluations around adaptive attacks, missing safety facts, and realistic visual tasks, while preserving existing baselines and recording dataset and model versions.

Another reading: The strongest competing reading is to make no process change: agentic observations fell across the recent versus prior window, and release summaries do not establish benchmark validity or production relevance.

  • S035 daily-average change in dataset observations: 32.29 observations per day
  • S036 daily-average change in evaluation observations: 15.0 observations per day
  • S037 daily-average change in benchmark observations: 12.43 observations per day
  • S038 daily-average change in agentic observations: -6.57 observations per day

What does today's evidence fail to show, and what would change the reading?

high confidence

This keyword-filtered feed does not establish field-wide momentum, benchmark quality, model improvement, or durable adoption; only a small subset of previously tracked artifacts seen today appeared in more than one source.

The reported download movements are not corroborated: each comes from one platform and covers its registry-listed full tracked span, not a one-day change. They show platform counts, not why people downloaded an artifact or whether it works.

Takeaway: The reading would change with repeated cross-source measurements, independent benchmark audits, reproducible model results, real usage evidence, restored connector coverage, and persistent shifts across comparable windows rather than isolated releases or discussion.

Another reading: A competing reading is that higher recent dataset, evaluation, and benchmark observations, plus cross-source discovery of several releases, justify earlier investigation. That supports triage, but not claims of performance or adoption.

  • S025 artifacts seen today that the radar had already tracked: 315
  • S026 tracked artifacts today seen by more than one data source: 11
  • S027 downloads change for lmarena-ai/leaderboard-dataset: 142,702.0 downloads
  • S028 downloads change for RoboDojo-Benchmark/RoboDojo: 132,336.0 downloads
  • S029 downloads change for vedangfake/chess-slm-benchmark: 18,793.0 downloads
  • S030 downloads change for alexshpunt/explicit-edit-benchmark: 17,562.0 downloads
  • S031 downloads change for hf-benchmarks/transformers: 10,991.0 downloads
  • S032 downloads change for Rapidata/text-to-svg-human-feedback-benchmark: -7,580.0 downloads
  • S033 downloads change for RyeAI/danish-asr-leaderboard: 6,404.0 downloads
  • S034 downloads change for Agnuxo/P2PCLAW-Innovative-Benchmark: 5,992.0 downloads
  • S035 daily-average change in dataset observations: 32.29 observations per day
  • S036 daily-average change in evaluation observations: 15.0 observations per day
  • S037 daily-average change in benchmark observations: 12.43 observations per day

Evidence sources

Where this came from, and what it does not cover

Built from the validated daily snapshot and its 630 evidence records.

Briefing model: gpt-5.6-sol.

It read 161 of 630 records.

This briefing received 161 selected evidence records from a 630-record keyword-filtered corpus, so it does not represent a full reading of today’s feed or the wider field. Brave, OpenReview, and Semantic Scholar were unavailable, and parts of the attention collection were stale or unread because of request failures. Findings therefore describe the captured artifacts, not overall release prevalence or adoption.