Do AI Agents Need Complex Tools for ML Engineering?

Peter Bubenik · Apple ML · · Source
Image for How Much of a Harness Does a Strong Agent Need for Autonomous ML Engineering?

Step-by-Step Teaching

Step 1: What is an MLE Agent?

Machine Learning Engineering (MLE) Agents are AI systems designed to autonomously perform ML tasks — like training models, tuning hyperparameters, or competing on leaderboards — without constant human intervention.

Analogy: Think of an MLE agent like a self-driving car for data science projects.


Step 2: What is a "Harness"?

A harness is the surrounding infrastructure built around a core AI model to help it perform better.

Harness ComponentPurpose
Multi-agent orchestratorsCoordinate multiple AI agents
Retrieval subagentsFetch relevant information
Memory systemsStore past context
Workflow managersStructure task execution

Analogy: The harness is like scaffolding around a building — it supports construction but isn't the building itself.


Step 3: What is a "Backbone LLM"?

The backbone is the core Large Language Model (e.g., GPT-4, Claude) that actually reasons and generates solutions.

[Harness Layer]  ←  orchestration, retrieval, memory
      ↓
[Backbone LLM]  ←  the actual reasoning engine
      ↓
[Output/Action]

Step 4: The Central Research Question

"Does adding more harness complexity actually improve performance?"

The researchers compared:

  • ✅ Complex harnesses — multi-agent systems, retrieval tools, elaborate pipelines
  • ✅ Minimal-harness coding agent — LLM with direct access to read, write, and bash commands only

Key constraint: Both used the same time budget and same backbone LLM


Step 5: The Key Finding

Complex Harness + Strong LLM
        ≈ (roughly equal to)
Minimal Harness + Same Strong LLM

Conclusion: The harness layers became redundant when the backbone model was strong enough.

Critical Insight: The backbone LLM is the primary driver of performance, not the complexity of surrounding machinery.


Step 6: How Did They Prove This? — Ablation Studies

An ablation study systematically removes components to measure their individual contribution.

Full System → Remove Component A → Measure performance change
Full System → Remove Component B → Measure performance change
Full System → Remove Component C → Measure performance change

What they found: Removing harness layers caused little to no performance drop, confirming they were not adding meaningful value.


Step 7: Why Does This Matter?

ImplicationExplanation
Engineering efficiencyBuilding complex harnesses wastes resources
Research directionFocus should shift to improving backbone models
Benchmark designCurrent MLE benchmarks may not reward complexity
Practical deploymentSimpler systems can match complex ones

Step 8: Connecting to Broader Context

The article also references related work:

  • SCLATE — addresses long-horizon, multi-session agent evaluation (where harnesses may matter more)
  • AgentBuilder — focuses on user experience design for agents

Key nuance: Harnesses may still matter in continual learning or multi-session settings — the finding applies specifically to current MLE benchmarks


Summary Mental Model

WRONG assumption:
More Harness Complexity → Better Performance

CORRECT finding:
Stronger Backbone LLM → Better Performance
Harness Complexity → Diminishing Returns (on current benchmarks)

Self-Check Questions

  1. What is the difference between a harness and a backbone LLM?
  2. Why did the researchers use equal time budgets in their comparison?
  3. What does an ablation study reveal?
  4. Under what conditions might harnesses still be valuable?
  5. What practical recommendation would you give an ML engineer based on this research?

More to study