THREAD · Object record
Google Chrome · Records and changes
Google’s web browser, with records of AI use, security fixes and release schedules.
00
Readings
Continue with the actual readings
Source
Starting with Chrome 153, major releases move from every four weeks to every two. Security patches also have their own cadence, and restarting remains an important step in applying downloaded updates.
02
Over time
Follow what happened next
Sources, developments and site topic updates carry separate labels. Earlier material and follow-ups stay in the same archive.
04
Connections
From models to tools and uses
- Chrome DevTools MCP
Chrome DevTools MCP connects coding agents to a real Chrome browser; tool and browser versions remain separate.
Connection sources
Chrome DevTools MCP: browser inspection and debugging for coding agents · Source ↗
Site records and collection notes
05
Collection note
Site records and collection notes
This page brings together retained information. An archive does not imply continuous monitoring of every development; new material joins it when collected.