Using AI Coding Agents to Surface Proposals for Interop 2027
Developers can audit local codebases to identify browser interoperability gaps before the deadline.
1Legacy Code and Interoperability
Web developers spend significant time maintaining legacy workarounds that modern platform features could replace. While Baseline expands constantly, cross-browser gaps still cause maintenance friction. Interop 2027 offers engineers a direct channel to influence browser engine priorities by submitting and upvoting web platform feature proposals before the submission window closes.
2September 23 Proposal Deadline
The proposal window for Interop 2027 closes on September 23. Browser vendors review community submissions to select focus areas for cross-browser parity. Developers must act quickly to submit well-vetted proposals or upvote existing ones, ensuring the most burdensome compatibility friction points receive priority implementation across all major browser engines.
3AI Coding Agents as Auditing Tools
Manually scanning GitHub issues for relevant proposals is time-consuming for engineering teams. Instead of manual triage, developers can configure AI coding agents in their terminal or IDE. These agents audit local codebases, identifying custom polyfills, wrapper libraries, and CSS conditional rules that signal missing web platform features.
4Automating Codebase Scans via MCP
The recommended audit workflow uses DevTools MCP to run a Lighthouse Baseline features inspection. The coding agent scans repository files for polyfills, wrapper libraries, and explicit fallback blocks. This process surfaces custom JavaScript hacks and vendor workarounds that could be eliminated if modern web standards were implemented consistently.
5Cross-Referencing Open GitHub Proposals
Agents query open issues in the web-platform-tests repository using the GitHub CLI focus-area-proposal label. The assistant matches existing submissions directly against the workarounds identified in your codebase. This automation highlights which open proposals your team should actively upvote to eliminate technical debt in your specific software projects.
6Vetting Unproposed Platform Features
For unaddressed compatibility gaps, the agent evaluates whether candidates meet official Interop submission standards. A valid proposal requires a stable W3C or WHATWG specification, at least one browser engine implementation, existing web platform tests, and no vendor blockers, ensuring proposed features have genuine traction before submission.
7Prioritizing Impact by Code Reduction
The prompt structures agent findings into prioritized tables sorted by estimated code and library elimination. By quantifying potential boilerplate removal, engineers can immediately identify which web platform capabilities offer the highest return on investment. Teams gain clear evidence regarding which proposals will streamline their production workflows most effectively.
8Directing Future Browser Standards
Participating in Interop 2027 enables development teams to directly influence the browser ecosystem. Leveraging AI assistants streamlines the discovery of legitimate platform gaps from existing repositories. Submitting vetted issues before September 23 ensures that collective engineering pain points translate into actionable cross-browser compatibility priorities for next year.
Original article: web.dev — Using AI Coding Agents to Surface Proposals for Interop 2027