for AI Agents
summary
Next.js exposes internal runtime state to agents via an MCP bridge so agents can query the dev server, inspect precise hydration mismatches, identify the exact source file behind intercepted routes, and run curated migrations to Next.js 16. Demos show an agent using Next Dev Tools MCP and tool calls like get_errors and get_page_metadata to fix a hydration error, add a loading state to the correct modal route, and orchestrate a full /upgrade-nextjs-16 migration workflow that automates most steps but leaves ~10% for human review.
AI-written summary · about
chapters (9)
- 0:00AI agent capabilities
- 1:37Dev tools for humans
- 4:24The context problem demo
- 7:12Initial solution limitations
- 11:03Next dev tools MCP
- 13:19Debugging with MCP
- 17:04Advanced code generation
- 22:25Automated app migration
- 24:26The future of AX
related talks
30mMCP DevTools: Giving Your AI Eyes
01h 28mAI Coding Agents and how to code them
25mThe Ai-Assisted Developer Workflow: Build Faster and Smarter Today
25mArchitecting AI in Angular: WebMCP, A2UI, and the Agent Experience
46mFullstack AI: The Building Blocks for Production Ready AI-Powered Software
19mYour Biggest User Isn't Human: Designing DevTools for AI Agents
01h 03mAI Coding Agents and how to code them
08mAI-Powered Development