Use parallel agents for a Solid-to-React rewrite

Cursor split an internal Solid-to-React migration across many agents so the codebase could be updated in parallel.

Done with Cursor· Advanced

What they did
Cursor applied its multi-agent system to its own code and used it to move the project from Solid to React without taking the app offline. Planning agents first examined the repository and broke the job into smaller assignments, then sub-planners narrowed those assignments further. Worker agents handled one assignment each and wrote their changes into the shared branch, while a judge agent checked each round and chose whether to keep the cycle going.
How it went
The effort lasted more than three weeks and ended with +266K/-193K edits. It made it through CI and initial checks, but the authors said it still needed a careful human review.
Tips
The team said the prompt design mattered more than the surrounding system or the models behind it. They also found that some agents wandered when left running too long, so occasional resets helped reduce drift.

Try it yourself with Cursor

I need to move [repo path] from [source framework] to [target framework] without a separate rewrite branch. First inspect the repository and divide the migration into small, independent tasks grouped by [directory, feature, or component]. Launch parallel background agents, give each one a single task, and have them report when the code compiles and the relevant tests pass. Before any step that would delete files, submit changes, or merge work, stop and ask me to approve it. When everything is finished, summarize the biggest changes and flag the areas that deserve the closest manual review.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on cursor.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.