AI Didn’t Kill the Web, It Moved in! — Olivier Leplus (AWS) & Yohan Lasorsa (Microsoft)
TL;DR
AI has permeated every stage of the web development lifecycle, from coding agents that use customizable "skills" to browser-native AI debugging tools, fundamentally shifting how developers build, test, and optimize applications.
🤖 Agentic Coding & Custom Skills 3 insights
Skills extend agent capabilities
Lightweight text-based plugins following open specifications allow coding agents to access domain-specific expertise and external tools like GitHub CLI or Playwright.
Workflow automation via agents.md
Developers can define repeatable workflows in a standard agents.md file, enabling autonomous implementation of features, video recording, tunnel creation, and mobile notifications.
Custom skill creation
Developers can build custom skills (e.g., sending Telegram notifications or creating public tunnels) to integrate personal workflows and external services into the agentic pipeline.
🔍 Browser Control via MCP 3 insights
Chrome DevTools MCP server
The Model Context Protocol (MCP) enables agents to programmatically control Chrome DevTools, allowing automated clicking, form filling, screenshots, and performance tracing.
Automated performance testing
Agents can simulate various network conditions (2G, 3G, fast internet) and generate detailed reports with Core Web Vitals metrics (LCP, CLS) and optimization recommendations.
Seamless IDE integration
MCP servers integrate directly into development environments, giving agents access to browser capabilities without manual intervention.
💻 Native AI in Browser DevTools 3 insights
Contextual error debugging
Chrome DevTools now features built-in AI assistance (when enabled) to explain console errors like CORS issues and suggest fixes directly within the browser.
Performance optimization insights
Developers can analyze network requests and performance traces using AI chat interfaces to identify render-blocking resources and optimize LCP scores.
Integrated debugging workflow
AI assistance eliminates context switching by allowing developers to debug failing requests and analyze CSS directly within familiar DevTools panels.
Bottom Line
Developers should adopt "skills" and MCP servers to automate their specific workflows while enabling AI features in browser DevTools to streamline debugging, as these integrations represent the new standard for efficient web development.
More from AI Engineer
View all
How METR measures Long Tasks and Experienced Open Source Dev Productivity - Joel Becker, METR
Joel Becker from METR argues that slowing compute growth would proportionally delay AI capabilities milestones measured by task time horizons, while presenting findings that experienced open-source developers showed minimal productivity gains from AI coding assistants like Cursor, challenging optimistic adoption curves.
Identity for AI Agents - Patrick Riley & Carlos Galan, Auth0
Auth0/Okta leaders Patrick Riley and Carlos Galan unveil new AI identity infrastructure including Token Vault for secure credential management and Async OAuth for human approvals, presenting a four-pillar framework to authenticate users and authorize autonomous agent actions across enterprise applications.
OpenAI + @Temporalio : Building Durable, Production Ready Agents - Cornelia Davis, Temporal
Cornelia Davis from Temporal demonstrates how integrating OpenAI's Agents SDK with Temporal's distributed systems platform creates production-ready AI agents that automatically handle crashes, retries, and state persistence without developers writing complex resilience code.
Your MCP Server is Bad (and you should feel bad) - Jeremiah Lowin, Prefect
Jeremiah Lowin argues that most MCP servers fail because developers treat them like REST APIs for humans rather than curated interfaces optimized for AI agents' specific constraints around discovery cost, iteration speed, and limited context windows.