Skip to content
Agents tracked: 258 Downloads (7d): 219M up 6.1% GitHub stars: 5.5M VS Code installs: 148M Releases (7d): 293 Agent status: 2 with issues Updated Oct 7, 2026
Showcase Cursor

Cursor's planner-worker agents built a web browser from scratch in about a week

Cursor tested long-running autonomous coding with a hierarchy of planner agents that create tasks and worker agents that just complete them. The headline project was a browser engine, published as FastRender.

The problem

Single agents stall or lose track on very large codebases. Cursor tried to find an agent structure that keeps hundreds of agents productive on one repository for weeks.

How they did it

  1. Planner agents explore the codebase, create tasks and start sub-planners for specific areas.
  2. Worker agents focus on finishing their assigned task and don't coordinate with each other.
  3. Every agent pushes to the same branch.

Results

  • The agents ran for close to a week, writing over 1 million lines of code across 1,000 files.
  • Hundreds of workers run concurrently, pushing to the same branch with minimal conflicts.
  • Other runs included a Solid-to-React migration in Cursor's own codebase (+266K/-193K edits), which the team says still needs careful review.

As reported by the source (Cursor Blog); AgentGid did not measure these figures.

Takeaway. Cursor found that simple planner-worker roles and good prompts mattered more than elaborate oversight layers.
AgentGid's take

This is a research-scale experiment, not a workflow to copy: running hundreds of concurrent agents for a week suits teams with deep engineering skill and a large model budget. Cursor's plans bill usage at model API rates with on-demand overage, so costs at that scale could climb fast. For smaller-scale agent work, Zed (open source, Free + $10/mo) lets you bring your own API keys.

The agent used here

Similar use cases

Guides