Cursor migrates kentcdodds.com to React Router
Kent C. Dodds used Cursor to upgrade dependencies and migrate his website from Remix 2 to React Router 7. After human testing and several correction rounds, he merged the migration into the main branch.
Original prompt
Shared by the source author. See source notes for context.
Upgrade us from Remix v2 to React Router v7. Before doing this, look up relevant migration docs/upgrade guides.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Kent C. Dodds
- Original account
- Read the source ↗
- Published
- 20 Feb 2026
- Source link checked
- 15 Oct 2026
- Reported result
- Kent C. Dodds used Cursor to upgrade dependencies and migrate his website from Remix 2 to React Router 7. After human testing and several correction rounds, he merged the migration into the main branch.
- Human involvement
- Dodds supplied route comparisons, requested repairs, tested changes locally and merged the migration after multiple review rounds.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Group outdated dependencies by difficulty and upgrade in stages.
- Research migration guides and implement the Remix-to-React-Router change in a background agent.
- Correct routing using old/new route output, address review findings and test before the human merge.
Kent C. Dodds used Cursor to upgrade dependencies and migrate his website from Remix 2 to React Router 7. After human testing and several correction rounds, he merged the migration into the main branch.
The work began by grouping outdated packages by upgrade difficulty. Easier updates came first, followed by individual major upgrades using migration documentation. For the framework change, Dodds selected a long-running background agent and supplied requirements covering related dependencies, existing patches and an alternative fetch strategy.
He also changed the routing convention. The first attempt produced an incorrect route structure, so Dodds gave the agent route listings from both branches and asked it to preserve the original structure under the new convention. The next attempt worked in his test. He then requested current React Router typing patterns and left the agent working overnight; that run lasted twenty-one minutes.
Bugbot and CodeRabbit identified additional issues. Dodds continued the agent repair loop, pulled the changes locally and tested the site before merging. The source credits existing tests and documentation with making this practical. It does not show that an unreviewed migration would have succeeded. The reported outcome combines autonomous research and edits with decisive human feedback, route comparisons and final acceptance.
Prompt
Original prompt
Source: kentcdodds.com · Kent C. Dodds
Frequently asked questions
What did the agent do?
It researched migration documentation, changed dependencies and routing, and repaired review findings in background sessions.
What remained the human’s responsibility?
Dodds supplied route comparisons, requested repairs, tested changes locally and merged the migration after multiple review rounds.
Why did Dodds supply route listings?
The first routing conversion was incorrect. Comparing listings from both branches gave the agent concrete evidence for preserving the original structure.
More details
About this account
Cursor researched migration guides, edited dependencies and routing, ran in the background and repaired issues surfaced by route comparisons and code review.
Firsthand account opened and read. Outcome is source-reported, not independently reproduced. Initial routing was wrong; human testing and multiple review-driven repairs preceded merge. Original published prompt excerpt, no more than 25 words.
Credit: Kent C. Dodds
Source published 20 Feb 2026
Source checked 15 Oct 2026
Tools and topics
React Router · Remix · Bugbot · CodeRabbit
React Router · Remix · Bugbot
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.