I tried to catch Next.js contradicting itself. It never did.
This is a submission for the Sanity Challenge, Path One: Ship an Agent That Queries Real Content What I Built Next.js has two routers. The Pages Router and the App Router answer the same questions in incompatible ways, and both sets of documentation are live, indexed, and correct. Neither page carries a banner saying "this is the old way." Search does not tell you which one you landed on. So an…
The story you've shared showcases an AI assistant called Router Rosetta, which translates Next.js code and queries between the Pages Router and the App Router while citing the official documentation for every claim. The assistant refuses to provide answers when the requested information is out of scope, such as configuring Redis session storage or custom Kubernetes ingress routing in Next.js.
Instead, it informs the user that the knowledge base does not cover these topics. The assistant is instructed to only answer from the structured content provided, rather than relying on its own memory of Next.js.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
