Find features to support for Interop 2027 with your coding agent

Web developers across the globe spend a significant portion of their engineering lifecycles untangling, maintaining, and supporting legacy codebases. Often, these developers are forced to rely on complex polyfills, custom JavaScript workarounds, and heavy wrapper libraries just to achieve consistent behavior across different web browsers. While modern web standards have evolved significantly—with more features entering the "Baseline" availability tier every month—gaps remain between what developers need to build modern applications and what the open web platform natively supports.

To bridge these persistent gaps, the web development community, browser vendors, and standards organizations are rallying around the Interop 2027 initiative. This multi-stakeholder effort is designed to identify, prioritize, and fix interoperability pain points that frustrate developers daily. However, actively participating in the proposal process has traditionally required tedious manual auditing, extensive cross-referencing of GitHub repositories, and digging through mountains of technical issues.

Now, a new approach is emerging that leverages modern AI tooling to streamline this workflow. By utilizing AI-powered coding agents directly within integrated development environments (IDEs) or terminal interfaces, developers can instantly scan their production codebases, identify missing web platform features, match them against open Interop proposals, and submit targeted advocacy before the critical September 23 deadline.

The Background and Context of Interop Initiatives

The Interop initiative series—preceded by Interop 2022, Interop 2023, Interop 2024, Interop 2025, and Interop 2026—was created to solve one of the most enduring challenges in web development: browser fragmentation. Historically, even when web specifications were officially published by organizations like the World Wide Web Consortium (W3C) or the Web Hypertext Application Technology Working Group (WHATWG), implementation timelines and behaviors varied wildly across browser engines such as Blink, Gecko, and WebKit.

These discrepancies forced developers to write defensive code, maintain browser-specific bug fixes, and deploy heavyweight workarounds that degraded overall web performance and bloated application bundles. Recognizing this friction, major browser vendors—including Apple, Google, Microsoft, and Mozilla—alongside independent browser makers and consultancy groups like Igalia, joined forces to establish coordinated testing and implementation goals.

The mechanism relies heavily on the Web Platform Tests (WPT) project. Each year, the community proposes a slate of focus areas. Features that achieve high interoperability scores across all participating browser engines graduate to stable, reliable components of the web ecosystem. By shifting the focus toward developer-reported pain points, the Interop program ensures that browser engineering resources are directed toward features that deliver immediate, real-world utility rather than theoretical specs.

The Countdown to Interop 2027 and the September 23 Deadline

The proposal cycle for Interop 2027 is currently underway, representing a vital window for engineers, product teams, and enterprise architects to influence the future trajectory of the web platform. However, the governance model requires strict adherence to timelines to allow adequate review, discussion, and scoring by browser vendors.

The most critical milestone in the current phase is the proposal submission deadline, which falls on September 23. After this date, the intake of new focus-area proposals closes, and the community transitions into evaluation, discussion, and final selection phases. Developers who miss this narrow window lose the opportunity to place their most pressing technical roadblocks onto the official tracking dashboard for the upcoming year.

In past cycles, thousands of developers have voiced their frustrations through GitHub issues, contributing to focus areas ranging from CSS nesting and container queries to subgrid and pointer events. For Interop 2027, the emphasis has expanded to include advanced web APIs, performance measurement tools, layout engines, and security primitives. Ensuring that a specific enterprise or community need is represented requires actionable data demonstrating how the absence of a feature impacts real-world codebases.

Leveraging Coding Agents to Audit Codebases for Web Gaps

Historically, auditing a large-scale enterprise codebase to identify missing platform features was a manual, error-prone endeavor. Developers had to manually inspect package.json files for known polyfills, search for @supports CSS conditional rules, and comb through custom utility libraries to deduce where native browser support was lacking.

With the rapid maturation of AI coding assistants and Model Context Protocol (MCP) integrations in developer environments, this auditing process can now be automated. Modern coding agents possess deep contextual awareness of project file structures, build configurations, and code patterns, making them uniquely suited to evaluate a project’s alignment with upcoming web standards.

By supplying a coding agent with a specialized prompt, developers can turn their local environment into an automated standards compliance and proposal-matching engine. A typical workflow executed by an AI agent involves several methodical steps:

1. Project Scanning: The agent analyzes the codebase using specialized tools—such as a Lighthouse "Baseline Features" audit via DevTools MCP—while simultaneously parsing source files for polyfills, wrapper libraries, explicit feature-detection blocks (@supports), and custom JavaScript fallback routines.
2. Proposal Matching: The agent connects to public repositories, querying active issue trackers (such as the official web-platform-tests/interop repository) to retrieve open focus-area proposals matching the project’s technical footprint.
3. Gap Identification: If the project relies on workarounds for features that lack an existing proposal, the agent flags these unproposed gaps, verifying that each candidate meets baseline criteria such as a stable W3C/WHATWG specification, at least one existing engine implementation, and comprehensive WPT test coverage.

The resulting output provides engineering teams with a prioritized summary table divided into two actionable categories: Proposals to Upvote (complete with metrics estimating the amount of legacy code and wrapper libraries that could be eliminated upon native implementation) and Vetted Features to Propose (backed by direct specification and test suite links).

Sample Audit Prompt for IDE and Terminal Coding Agents

To replicate this workflow, developers can utilize standardized prompts designed to guide their preferred coding assistant. The following prompt structure can be executed within terminal-based or IDE-integrated AI agents to audit any web project for Interop 2027 alignment:

Audit this codebase for Interop 2027 alignment:

1. Scan the Project:
   - Run a Lighthouse "Baseline Features" audit using DevTools MCP.
   - Scan files for polyfills, wrapper libs, @supports blocks, and custom JS workarounds.

2. Match open proposals:
   - Fetch open proposals using `gh issue list -R web-platform-tests/interop -l focus-area-proposal -s open`.
   - List proposals that directly match features used or would be using if not for compat issues.

3. Find Unproposed Gaps:
   - Identify platform features we need that lack an Interop 2027 proposal.
   - Verify each candidate has a stable spec (W3C/WHATWG), ≥1 engine implementation, WPT tests, and no vendor blockers.
   - Refer to https://github.com/web-platform-tests/interop/blob/main/proposal_guide.md for more information on what makes a good proposal.

Output: A summary table of Proposals to Upvote (with estimated code/libs eliminated) and Vetted Features to Propose (with spec/WPT links). Sort both tables by highest impact in descending order, with impact measured as estimated code/libs eliminated.

When executed, this prompt empowers the AI agent to synthesize abstract standards discussions with concrete, data-driven evidence derived directly from production codebases. Instead of relying on anecdotal claims of browser incompatibility, developers can present browser vendors with quantifiable proof of technical debt caused by missing platform features.

Implications for Enterprise Architecture and Developer Productivity

The integration of automated tooling into web standards advocacy marks a significant evolution in how the developer community interacts with browser vendors. For years, standards bodies operated with a degree of separation from everyday application developers, leading to a disconnect between theoretical specifications and practical implementation realities.

By utilizing coding agents to aggregate feature requests across thousands of distinct projects, the web development ecosystem gains a clearer, empirically driven consensus on which interoperability issues exact the highest toll on productivity and performance.

For enterprise organizations maintaining massive web applications, the stakes are particularly high. Legacy codebases often harbor millions of lines of JavaScript dedicated entirely to cross-browser normalization. When fundamental layout, styling, or scripting features achieve true interoperability, organizations can safely deprecate entire categories of internal helper libraries, reducing bundle sizes, improving execution speeds, and minimizing security vulnerabilities associated with unmaintained third-party polyfills.

Furthermore, streamlining the advocacy process democratizes participation. Smaller development shops and independent creators, who previously lacked the bandwidth to monitor standards committees and draft formal proposals, can now leverage AI assistants to articulate their technical needs with the rigor expected by browser engine contributors.

Conclusion and Immediate Call to Action

The Interop 2027 initiative represents a collective commitment to making the open web platform more predictable, reliable, and powerful. However, the success of the program depends entirely on active engagement from the developers who build for the web every day.

With the proposal submission window closing sharply on September 23, time is of the essence. Developers are encouraged to deploy coding assistants across their repositories, generate data-driven impact assessments, and participate in the official proposal and upvoting process on GitHub. By combining modern AI workflows with collaborative web standards governance, the developer community can actively shape a faster, more cohesive web platform for years to come.