AI Automation Broke Down on a 90-Component Migration Until the Verification Loop Got a 12x Rewrite
AI coding agents are only as fast as their feedback loops. A verification step built around visual inspection and cold restarts can multiply token costs and wall-clock time by an order of magnitude, making automation economically irrational. Swapping screenshots for scripted assertions turns a grinding bottleneck into a fast, auditable pipeline that makes large-scale migration actually feasible.
Migrating a 90-component cross-platform UI library to uni-app x means rewriting every file in UTS, UCSS, and uvue—a repetitive engineering grind that looked like a perfect job for an AI agent. The initial workflow had the agent restart a dev server, take screenshots, and visually inspect output after every change, a stateless loop that burned tokens and turned a single component fix into an afternoon affair. At that pace, the full migration risked stretching past a month, with credit consumption spiking dozens of times higher than expected. The bottleneck was not model intelligence but a verification step designed for human eyes. Replacing restarts with a persistent service, screenshots with a script that asserts layout properties and interface completeness, and manual records with the script's own output collapsed a ~240-second cycle into a stable ~19 seconds. The same seven-round troubleshooting session that once took 28 minutes now finishes in just over two, and the speed gain changed what tasks felt safe to delegate.
AI agent workflows that look automated on paper often hide a manual bottleneck in the verification step—visual inspection by screenshot is slow, expensive, and stateless by default.
The difference between a usable AI pipeline and a cost sink is rarely the model; it is whether the feedback loop is designed for a machine or a human.
Persistent state and scripted assertions are force multipliers for AI coding agents, turning a loop that burns tokens into one that produces auditable, repeatable results.
Speed changes risk tolerance: when verification takes seconds instead of minutes, developers delegate harder problems to the agent rather than hoarding safe, trivial tasks.
Ultimately, the official ecosystem is just too poor. uni-agent is a toy. Look at the deveco-cli released by HarmonyOS next door. For many things the AI doesn't know, it can verify directly through deveco-cli, and the AI can then follow the specifications.
uniappx has been out for how many years and it's still like this. Too few users, too many pitfalls. It feels like the uts language has deviated significantly from standard writing. There are too few references, and the AI can't figure it out either. Multi-platform compatibility is just too hard to do.
The officials don't put their heart into it. Some of the Vue syntax in the official documentation is outdated, and the docs are a mess. Just like Tencent's Kuikly—promoted as powerful and strong, but the open-source demos can only draw simple pages. It's not easy to use, and when you can't see any hope, not many developers are willing to invest their time.