Use Claude Code for a carefully checked migration

A developer used Claude Code to update a reset feature, but the review work and cleanup erased most of the speed gains.

Done with Claude Code· Intermediate· Oct 2026

What they did
The developer started by having Claude Code, through its harness and work API tokens, outline the job. Next, they asked the latest Opus model to move a web app’s account recovery path off older tools and onto newer ones. They watched each suggestion closely, then spent extra time fixing up the result afterward.
How it went
The output was acceptable for small pieces, but the overall design still missed the mark, and the agent also wandered into unrelated edits. The effort took about half a working day and roughly two months of Pro subscription cost, and it finished a little behind hand editing.
Tips
This approach works best when the change is tightly scoped and someone can inspect every step. Without that oversight, it would have introduced several subtle mistakes and more off-target edits.

Try it yourself with Claude Code

In [repo name], update the code that handles forgotten-password resets in [file, folder, or feature] so it uses [modern library] instead of [older library or pattern]. First, draft a short plan and name the files you expect to touch, then stop and wait for my approval. Limit yourself to the password-reset path, run the current tests after each meaningful change, and before you remove anything, submit anything, send anything, or touch unrelated code, pause and ask me to confirm. When the tests are green, give me a concise summary of the diff and any remaining risks.

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

Read the original on news.ycombinator.com ↗

Get 3 agent uses like this every morning

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