Engineering

Why Synthetic Data Is the Real Bottleneck for Computer Use Agents

David Park||7 min
+Enter

Building computer use agents feels like an arms race. Teams race to release agents that can browse, click, and automate workflows. But the real bottleneck isn't model compute or inference speed. It's data. Real-world interaction data is too scarce, too risky, and too expensive to scale. Synthetic data promises a solution, but only if it's accurate and realistic. Most teams mistake volume for quality and wind up with agents that hallucinate clicks or fail on basic tasks.

The data gap is concrete

Industry benchmarks show a stark gap between available training trajectories and what agents actually need. For a well-known web automation task, successful agents typically need access to 5,000 to 10,000 high-quality interaction trajectories. Most organizations have fewer than 500 annotated examples. That's a 10x to 20x shortfall. The gap widens when you account for edge cases, error handling, and multi-step workflows. Many teams resort to low-quality scraping, which rarely captures the nuance of adaptive behavior or error recovery.

Real data comes with hidden costs

Collecting real interaction data has a steep price. A typical data pipeline includes: (1) securing production environments, (2) designing clickstream capture pipelines, (3) labeling trajectories with intent and success states, (4) ensuring compliance and privacy, and (5) maintaining a feedback loop. Compliance and data governance alone can add 30 to 40 percent to the budget. If you rely on third-party datasets, licensing fees and usage restrictions often mean you cannot use data in production or share it internally. That limits what you can actually train on.

Synthetic data is only as good as its simulation

Not all synthetic data is equally useful. The quality of a synthetic dataset hinges on three factors: dynamics fidelity, action diversity, and trajectory continuity. If a simulator cannot reproduce realistic timing, navigation, or error states, the resulting agent will fail when it encounters the real world. For example, a browser simulator that always waits exactly one second between clicks will not prepare an agent for variable network latency or human-like pauses. Recent research shows that agents trained on high-fidelity synthetic trajectories can reach comparable performance to those trained on real data, but only when the synthetic data includes edge cases and error recovery. Purely template-based generation creates brittle policies that break on small variations.

The bottleneck isn't just having more data. It's having data that truly reflects the complexity and unpredictability of real interaction.

How Coasty fits

Coasty runs computer use agents on real desktops and browsers to capture realistic interaction data and generate synthetic datasets. The approach bypasses simplistic simulators and instead produces trajectories that reflect actual navigation patterns, timing, and error recovery. Because the data originates from real environments, it retains nuance that generic benchmarks often miss. Coasty works as a custom, contact-led service. The team designs datasets aligned with your specific tasks, domains, and evaluation criteria. This means you don't get a one-size-fits-all product. Instead, you get tailored synthetic data that matches the complexity of your target workflows.

If you're building computer use agents and hitting a wall with real-world data, synthetic data can close the gap, but only with careful design and realistic fidelity. The next step is to talk to the Coasty data team. Book a data call to discuss your use case, review possible dataset designs, and explore how Coasty's custom synthetic data service can accelerate your agent development at https://cal.com/coasty/coasty-data-call .

Want to see this in action?

View Case Studies
Try Coasty Free