---
type: "post"
id: "chrome-releases-modern-web-guidance-1-0-with-977b2e"
slug: "chrome-releases-modern-web-guidance-1-0-with-977b2e"
title: "Chrome releases Modern Web Guidance 1.0 with Firefox and Edge joining the project"
description: "Google says Modern Web Guidance 1.0 is now stable, with a workflow that scans existing web projects for selected modernization opportunities and guides coding agents through changes."
retrieval_nugget: "Google says Modern Web Guidance 1.0 is now stable, with a workflow that scans existing web projects for selected modernization opportunities and guides coding agents through changes."
published_at: "2026-11-11"
updated_at: "2026-11-11"
record_date: "2026-11-11"
date_kind: "published_at"
topics: ["google","coding-agents"]
entities: ["Google Chrome","Modern Web Guidance","Firefox","Microsoft Edge","Chrome DevTools","MetaMask","Paisabazaar","Tencent"]
related_patterns: ["skills-become-portable-capability-layer"]
novelty_label: "new_fact"
what_changed: "Modern Web Guidance is now stable at version 1.0, with Firefox and Edge joining the project."
prior_refs: ["https://newruntime.com/posts/google-chrome-s-modern-web-guidance-packages-expert-727856/"]
source_url: "https://developer.chrome.com/blog/modern-web-guidance-v1"
source_urls: ["https://developer.chrome.com/blog/modern-web-guidance-v1"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:chrome-releases-modern-web-guidance-1-0-with-977b2e"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/chrome-releases-modern-web-guidance-1-0-with-977b2e/","markdown":"https://newruntime.com/posts/chrome-releases-modern-web-guidance-1-0-with-977b2e.md","json":"https://newruntime.com/posts/chrome-releases-modern-web-guidance-1-0-with-977b2e.json"}
markdown_url: "https://newruntime.com/posts/chrome-releases-modern-web-guidance-1-0-with-977b2e.md"
---

# Chrome releases Modern Web Guidance 1.0 with Firefox and Edge joining the project

## Retrieval answer

Google says Modern Web Guidance 1.0 is now stable, with a workflow that scans existing web projects for selected modernization opportunities and guides coding agents through changes.

## Summary
Google says Modern Web Guidance 1.0 is now stable, with a workflow that scans existing web projects for selected modernization opportunities and guides coding agents through changes. Firefox and Edge have joined the project alongside Chrome. For teams building with AI, the release offers a way to put reviewed web-platform guidance into an agent workflow and inspect the company’s reported evaluation results.

## What happened
Chrome for Developers announced Modern Web Guidance 1.0 on November 10, 2026. The project packages web-platform expertise, development best practices, and browser-compatibility information as skills for coding agents. Google introduced an early preview at Google I/O in May; this release marks the stable 1.0 version. The announcement presents the tool as usable with different models and agent harnesses rather than tied to one model.

The headline addition is a modernization workflow for existing projects. It can analyze HTML, CSS, JavaScript, and `package.json` to identify opportunities for safe upgrades, then guide an agent through changes. Google says the first release uses static analysis to check a limited set of patterns, chosen to produce predictable results. The company says it intends to expand coverage, including agentic checks in which an agent reasons directly about a codebase rather than only matching known patterns. The announcement does not provide a price; it gives CLI commands for installation and updating: `npx modern-web-guidance@latest install` and `npx modern-web-guidance@latest update`.

Version 1.0 also includes an expanded guide database addressing hundreds of identified knowledge gaps, according to Google. Each guide has received deeper review from human experts, including technical leads for content areas and accessibility specialists. The company says it has completed evaluation coverage for all its guides and made a public evaluation dashboard available to show measurable improvements compared with agents without Modern Web Guidance. The announcement calls the project cross-browser: Firefox and Edge are joining Chrome to support compatibility and contribute to the work.

The guidance covers areas where Google says coding agents can miss established practices: accessibility, user experience, performance, and security. Its examples include keyboard focus, reduced-motion support, form validation, main-thread task scheduling, secure HTML sanitization, and credential management for passkeys. It also aims to help agents choose native HTML or CSS features when those suit a task better than custom JavaScript, with recommendations informed by Baseline and browser-compatibility data.

Google recommends pairing the skills with Chrome DevTools for agents. In its description, Modern Web Guidance supplies implementation expertise, while DevTools provides runtime visibility to verify, debug, and optimize code. Google’s examples include testing performance on a simulated low-end CPU, checking animations with reduced-motion preferences, and looking for memory leaks in cached views. The announcement reports results from adopters, including MetaMask’s five-week trial: its bot reviewed about 480 pull requests, commented on 64, and helped engineers resolve 43 findings, with a median 15 minutes from comment to fix. These are company-reported examples, not independent measurements.

## What the archive adds
New Runtime’s earlier coverage on [Chrome’s Modern Web Guidance](https://newruntime.com/posts/google-chrome-s-modern-web-guidance-packages-expert-727856/) described expert-curated web recommendations packaged as skills that coding agents can retrieve through a CLI (November 11, 2026). This is a new release on a known story: the stable version adds codebase modernization, broader guide coverage, a public evaluation dashboard, and contributions from Firefox and Edge.

## Trend signal
This release supports [skills becoming a portable capability layer](https://newruntime.com/patterns/skills-become-portable-capability-layer/). Google says the guidance can be installed through a CLI or popular agent-plugin marketplaces, and positions it for use across models and agent harnesses. Portability alone does not demonstrate that the skills work consistently across those environments; the release’s public evaluations and real project trials are relevant signals, but broader independent testing remains important.

## Why now
Google’s announcement frames the release around the shift to agentic web development and the accumulation of legacy workarounds in existing codebases. Its stable milestone is also when Firefox and Edge join the effort, widening the compatibility remit beyond Chrome. The announcement does not give a separate deadline or explain a time-limited rollout.

## Connections to other events
New Runtime’s earlier coverage on [browser release cadence](https://newruntime.com/posts/both-firefox-and-google-chrome-now-ship-updates-aaf7b3/) described Firefox’s planned weekly dot-release opportunities alongside its four-week major-release cycle (October 30, 2026). That story concerns browser update schedules, not agent skills, but it provides context for why compatibility guidance must keep pace with changes across browser engines. Modern Web Guidance’s cross-browser contributions address that moving target at the level of recommendations for developers.

## Why it matters
An agent can produce code that runs while still missing a better native platform feature, an accessibility requirement, or a compatibility constraint. A maintained set of reviewed recommendations gives teams a way to make some of that expertise available during implementation rather than relying entirely on a reviewer to catch it later. The modernization workflow is especially relevant to production code, where safe upgrades may matter more than generating a greenfield screen.

The limits matter too. Static analysis over a bounded set of patterns is not a general audit of a codebase, and guidance is not proof that a change works in the finished application. Google itself recommends verification with runtime tools. Teams should treat the skills as an additional reviewer and source of suggestions, then retain tests, accessibility checks, browser coverage, and human ownership of changes. The reported adopter results make the workflow worth evaluating; they do not establish that the same savings or quality gains will transfer to every stack.

## What happens next
- **Modern Web Guidance will add more modernization patterns beyond its initial static-analysis scope** (6 months, 70%). Watch for: a release describing expanded pattern coverage or agentic codebase checks.
- **The project will publish evaluation results that distinguish performance across supported agent environments** (6 months, 55%). Watch for: dashboard results broken down by harness or model rather than only a general comparison.

## Limits and uncertainty
The announcement describes the modernization workflow as deliberately limited, but does not enumerate every pattern it currently checks in the article. Google’s public evaluation dashboard is cited, yet the announcement’s claims do not independently establish how representative its tests are or whether gains persist across projects, models, and agent harnesses. Adopter examples are reported by Google and the participating organizations; no independent audit of the claimed time savings or quality improvements is included. The announcement also does not state a price.

## Skill to build now
Pick one existing web project and run the modernization workflow in a branch rather than directly on your main line. Ask the agent to explain each suggested change, then test the result against the browsers and accessibility requirements your product actually supports. Record which recommendations were useful, which required manual correction, and whether existing tests caught regressions. That small evaluation can show whether the guidance fits your codebase before you make it part of a broader workflow.

## Reader takeaway
Modern Web Guidance 1.0 gives web teams a cross-browser-oriented set of expert-reviewed skills and a bounded way to look for modernization work in existing projects. Treat it as an aid to coding and review, not as a substitute for running the application, testing accessibility, or verifying browser behavior.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Google](https://newruntime.com/topics/google.md): Explore the google topic hub.
- topic hub: [Coding Agents](https://newruntime.com/topics/coding-agents.md): Explore the coding-agents topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)