Skip to content

WebDancer & WebThinker: Training a Deep Research Agent from Scratch

Sep 19, 20261 min
TL;DRTwo NeurIPS 2025 papers answer the same question: how to train a web research agent from scratch? WebThinker chooses 'bolt on web capability to existing reasoning models,' WebDancer chooses 'rebuild everything from data construction to RL training.' Two philosophies, four stages, one core insight: training beats prompting.

🌏 中文版

Last article's panorama mapped the four core components of Deep Research systems. This article zooms into one of them: training methodology. Two NeurIPS 2025 papers take fundamentally different philosophies to train agents that can autonomously research the web from scratch.

Both face the same question: how does an agent learn to autonomously search, navigate, synthesize, and produce research reports across the web?

  • WebThinker (arXiv:2504.21776): Augment existing Large Reasoning Models (LRMs like QwQ-32B, DeepSeek-R1) with web exploration capability.
  • WebDancer (arXiv:2505.22648): Rebuild from scratch — data construction, trajectory sampling, supervised initialization, and RL fine-tuning, end to end.

These aren't just technical differences — they're fundamentally different answers to what a deep research agent is.

Two Training Philosophies

DimensionWebThinkerWebDancer
Starting pointExisting LRM (QwQ-32B / DeepSeek-R1)From scratch
Core approachAdd-on module (Deep Web Explorer)End-to-end four-stage pipeline
TrainingOnline DPO (reinforce tool use)SFT cold-start → DAPO RL
FormatThink-Search-Draft interleavingReAct
Best forRapidly enhancing existing modelsBuilding specialized agent models

WebThinker: Give Reasoning Models Web Eyes

WebThinker's core hypothesis: LRMs already know how to "think," but not how to "find." They have powerful internal reasoning but are constrained by static knowledge — they stall when facing tasks requiring real-time information or cross-source synthesis.

The solution is three modules:

1. Deep Web Explorer

When the model detects a "knowledge gap," it automatically triggers web exploration: search → navigate → extract. This module doesn't interfere with normal reasoning; it only intervenes when needed.

2. Autonomous Think-Search-and-Draft

The model naturally interleaves three behaviors during thinking:

  • Think: Reason, analyze, identify knowledge gaps
  • Search: Trigger web exploration to fill gaps
  • Draft: Write evidence into the report

The entire process completes in a single generation — no external orchestrator to interrupt and restart.

3. Online DPO Training

Direct Preference Optimization reinforces tool usage:

  • Generate multiple possible reasoning paths (some search, some don't)
  • Compare outcomes of these paths
  • Prefer paths that are accurate and efficient (not just correct answers, but concise reasoning too)

This is "online" — training data updates continuously, not trained on a fixed dataset in one pass.

Benchmark performance (WebThinker-32B-RL):

BenchmarkScorevs. Baseline
GPQA70.7%Beats all baselines
GAIA48.5%+8.5% over base
WebWalkerQA (overall)46.5%Hardest sub-question: 15.8%
HLE15.8%Surpasses o3-mini (High)

WebThinker-R1-7B achieved 174.4% (GAIA) and 422.6% (WebWalkerQA) relative gains over direct generation.

WebDancer: Four Stages from Zero

WebDancer chose the harder road: not relying on any pre-trained reasoning ability, rebuilding everything from data and training pipeline.

Four-Stage Pipeline

StageWhatWhy
1. Browsing data constructionBuild large-scale browsing trajectory dataTraining material
2. Trajectories samplingSample diverse interaction trajectories from dataCover multiple task types
3. SFT cold-startSupervised fine-tuning for initial capabilityAvoid RL instability from scratch
4. RL (DAPO) generalizationEnhance generalizationSurpass teacher model performance

Why SFT?

WebDancer's paper explicitly states: training web agents with RL from scratch is unstable. Environment reward signals are sparse (only success/failure at the final step), and the model learns almost nothing in early stages.

So they use SFT first to build "cold-start" capability — giving the model a sense of what "searching, clicking, reading, synthesizing" feels like — then use RL to refine on top.

Architecture

Instantiated as WebDancer based on ReAct format:

  • Observe web state
  • Reason about next action
  • Execute action (click, type, scroll)
  • Adjust based on feedback

Benchmark performance (WebDancer-32B):

BenchmarkPass@1Pass@3
GAIA51.5%64.1%
WebWalkerQA47.9%62.0%

They later released WebSailor (June 2025), achieving open-source SOTA on more difficult browsing benchmarks.

The Fundamental Difference

On the surface, both approaches use RL and perform well on GAIA/WebWalker. But they answer different questions:

WebThinker answers: "I already have a powerful reasoning model, how do I give it web capability?" → Add-on module + Online DPO. Advantage: fast, leverages existing model investment. Cost: constrained by the underlying model's architecture.

WebDancer answers: "How do I build a specialized web research agent from the ground up?" → Full pipeline + SFT + RL. Advantage: can optimize every layer for the task. Cost: requires massive data and training resources.

Shared Conclusion

Regardless of the path, both papers point to the same finding:

End-to-end training (RL/SFT) produces agents with higher ceilings than hand-crafted workflows.

WebThinker proves that even on existing powerful models, adding RL-trained tool usage creates a qualitative shift. WebDancer goes further, proving that training from scratch can break through even higher ceilings.

This directly maps to the optimization paradigms in last article's three-stage roadmap: workflow prompting is the convenient starting point, SFT is the practical middle ground, and end-to-end RL is theoretically the most elegant ceiling.

What's Next

These two focus on "how to train agents." Subsequent articles will cover "how to keep agents learning" (IterResearch, AREX) and "how to optimize planning" (WebWeaver, DeepPlanner).

參考資料