On the plus side, you have the AI to ask for explanations. It’s not a bad way to learn about development, so long as you are willing to slow down and do the mental work. Ultimately, there’s no shortcut around learning the tech if you are ultimately in charge of guiding the AI towards a maintainable solution.

In any case, the AI will continue to do the work it needs to do, like run npm install. It will also display diffs of code files and give you the chance to “keep” or “skip” them individually. It will even find and fix bugs for you. For example, my build encountered a typical node-gyp error on Windows. The agent offered to fix it, and after approval the error was resolved.

Review the agent’s work — or let the agent review its work

Once you approve the final diff, the AI wraps up its routine. Now we can re-run the app in the terminal with npm run dev, and this time, try clicking the hyperlink in the console. If all is well, the IDE will helpfully open the app in a preview tab. However, I encounter an error: