Back to Feed
Agents / Benchmarks & Evals

Benchmarking AI Agents for Data Science

Original: DSAgentBench: Can Agents Automate End-to-End Data-Science Workflows in Real Computer Environments?

Listen to the summary

Uses a voice available on your device

Audio options
On this page 4 sections
Related concepts 3 concepts

Key Takeaways

  • Existing benchmarks fail to capture the complexity of multi-stage, multi-tool data science workflows in real computing environments.
  • The new benchmark features 275 human-authored tasks requiring iterative analytical reasoning and interaction with tools like Jupyter Notebook and SQLite.
  • Claude-4.6-Sonnet achieved the highest success rate of 56.70% by leveraging both visual screenshots and accessibility trees.
  • Open-source agents currently struggle significantly, with all tested models achieving success rates below 1%.

Summary & Methodology Analysis

The researchers extended the existing OSWorld framework to support a realistic data science stack, including Jupyter Notebook, SQLite, and external data connectors for platforms like Kaggle and OpenML. The environment simulates an Ubuntu virtual machine where agents are evaluated on their ability to navigate file systems and manage tool coordination. Unlike previous benchmarks that rely on surface-level code execution, this system uses a deterministic, execution-based evaluation to verify the actual analytical correctness of the generated outputs. This methodology forces agents to perform iterative analytical reasoning rather than simply predicting isolated code snippets. Agents interact with the desktop via a GUI action space, utilizing both visual screenshots and accessibility trees as primary inputs for decision-making. The evaluation focuses on end-to-end workflows that mirror actual data science tasks. The current performance leaders are proprietary models, specifically Claude-4.6-Sonnet, which hit a 56.70% success rate under the combined screenshot and accessibility tree setting. In contrast, the open-source landscape remains nascent for this specific application, with all evaluated open-source models failing to exceed a 1% success rate. The study acknowledges significant limitations regarding open-source agents, as they currently lack support for accessibility tree observations and are restricted to screenshot-only inputs. Furthermore, the qualitative error analysis is confined to a subset of trajectories, which may exclude rare failure patterns in the agent workflows.

Interactive System Flowchart

Click diagram to expand and zoom

Cross-Examination & FAQs

A deeper dive clarifying mechanics, constraints, and baseline evaluations.

Q1. What is the primary purpose of DSAgentBench?

It is designed to evaluate whether AI agents can automate multi-stage, multi-tool, end-to-end data science workflows in realistic computer environments.

Q2. How are the agents tested in this benchmark?

Agents are deployed in an Ubuntu virtual machine and must navigate file systems, coordinate tools, and perform iterative analytical reasoning to complete 275 human-authored tasks.

Q3. How does this benchmark differ from previous ones?

It focuses on realistic computer interaction rather than surface-level code execution, utilizing a deterministic, execution-based system to verify analytical correctness.

Q4. What tools are integrated into the testing environment?

The environment includes Jupyter Notebook, SQLite, and access to external data sources such as the Kaggle API and OpenML.

Q5. How do agents perceive the computing environment?

Agents interact via visual observations based on screenshots and accessibility trees using a GUI action space.

Q6. Which model performed the best in this evaluation?

Claude-4.6-Sonnet achieved the highest task success rate at 56.70%.

Q7. Why are open-source models performing poorly?

Open-source agents currently do not support accessibility tree observations, limiting them to screenshot-only settings which significantly hinders their success rates.

Q8. Are there limitations to the error analysis provided in the paper?

Yes, the qualitative error analysis is based on a subset of the total task trajectories, which potentially misses rare failure patterns.

Q9. Does the paper specify the inference latency or cost for these models?

The paper does not specify latency or monetary cost figures for the models tested.