Back to Feed
Agents / Benchmarks & Evals

Improving Web Agent Performance via Co-Synthesis

Original: SynWeaver: Website-Prior Task and Trajectory Co-Synthesis for Web Agents

Listen to the summary

Uses a voice available on your device

Audio options
On this page 4 sections
Related concepts 5 concepts

Key Takeaways

  • SynWeaver addresses poor generalization in web agents by jointly generating website-prior-based task intents and execution trajectories.
  • The method uses DFS-based crawling to build a structured website map, providing granular supervision for fine-tuning UI-aware models.
  • On the WebArena benchmark, the approach achieved a 19.91 success rate with Qwen3-VL-8B-Instruct and 14.16 with InternVL3-8B.
  • SynWeaver outperformed the strongest baseline on WebVoyager by 4.64 points, reaching a 27.06 success rate.
  • The pipeline includes programmatic post-verification checks for termination, validity, and consistency to ensure high-quality training data.

Summary & Methodology Analysis

SynWeaver tackles the inability of web agents to handle unseen sites by creating website-specific supervision. The process begins with a DFS-based crawler that maps the target website to identify distinct UI states and transitions. This map provides the necessary data to fine-tune UI-aware models, which are neural networks adjusted to understand and interact with interface elements. By leveraging this structured map, the system derives page-level and transition-level supervision, transforming raw website interactions into actionable data for the agents. The core innovation lies in the collaborative task-trajectory synthesis, where the system updates task intents and execution prefixes simultaneously using a teacher model to ensure consistency. This dual-optimization strategy reduces hallucinated task proposals that typically plague agents when navigating unfamiliar environments. The pipeline further enhances data quality through a reconstruction loop that triggers programmatic checks, specifically verifying termination, validity, and consistency, whenever a task-trajectory pair fails. This allows for the iterative expansion of the dataset by resampling transitions and prompting the model to generate a wider variety of tasks. Regarding performance, the method shows robust results on standard benchmarks. On WebArena, the approach reaches a 19.91 success rate using Qwen3-VL-8B-Instruct and 14.16 using InternVL3-8B. On WebVoyager, it achieves a 27.06 success rate, representing a 4.64 point lead over the strongest existing baseline. However, the system faces practical limitations in production scenarios. Since it relies on automated crawling, it is currently vulnerable to anti-bot measures like CAPTCHAs, rate limiting, and dynamic authentication. Furthermore, the student models remain constrained by the reasoning and interaction performance of the proprietary teacher models employed during synthesis.

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 goal of SynWeaver?

The goal is to enable web agents to generalize better to unseen websites by generating website-specific supervision for training.

Q2. How does this improve agent performance?

It reduces hallucinated task proposals and improves trajectory synthesis through collaborative, intent-driven generation.

Q3. Does this require manual labeling of websites?

No, it uses automated DFS-based crawling to construct a structured map of the website for supervision.

Q4. What are the core technical components of the synthesis process?

The process includes DFS-based crawling, fine-tuning of UI-aware models, collaborative synthesis of task intents and trajectories, and programmatic post-verification.

Q5. What benchmarks were used to evaluate this method?

The paper uses WebArena and WebVoyager to evaluate performance.

Q6. What models were used in the evaluation?

The evaluation utilized Qwen3-VL-8B-Instruct and InternVL3-8B.

Q7. What happens if a generated task-trajectory pair fails verification?

The system runs a reconstruction loop to attempt to correct the pair based on post-verification checks for termination, validity, and consistency.

Q8. What are the limitations regarding website crawling?

The maps are constructed via automated crawling, which is less reliable against anti-bot mechanisms like CAPTCHAs, rate limiting, or dynamic authentication.

Q9. Are there limitations to the student models?

Yes, the student models are bounded by the reasoning and interaction capabilities of the proprietary teacher models used for synthesis.

Flag an issue

What is wrong with this summary?

What is wrong?