✦ CodeYourVibe

Dev Tools

Chrome DevTools adds safer controls for coding agents

The October 2026 DevTools update gives agents finer control over JavaScript execution, source maps, heap snapshots and browser automation. An evergreen explainer based on Chrome's 22 September 2026 recap; this is not a new announcement today.

By ·

Editorial cover for the news story: Safer controls for coding agents
Editorial cover built around an official brand mark. Story source.

What Changed

Chrome's October 2026 DevTools roundup covers features shipped in Chrome 153 and 154. The Chrome DevTools MCP server gained Agent Plugins 1.0 support, a --no-javascript-evaluation option, on-demand source maps, configurable filesystem roots and a query_heapsnapshot tool. The Performance panel now supports software-navigation analysis and calibrated CPU performance overrides through CDP. The Application panel has an Ads view for ad scripts and the experimental CrUX ad metrics, while Elements adds inactive-style support and keyboard-accessible adornments. The post was published on 22 September 2026.

Why It Matters

Coding agents increasingly drive real browsers, and broad JavaScript evaluation is a dangerous default: a page or prompt can turn a debugging session into arbitrary execution. Being able to disable evaluation, defer source maps and constrain filesystem paths makes agent-assisted debugging easier to audit. The memory and performance tools also matter for AI-generated pages that look correct but leak or run slowly. These are browser-tooling improvements, not a security boundary for your application; they reduce accidental exposure but do not replace sandboxing.

Practical Impact

Update Chrome and the chrome-devtools-mcp package, then review the flags your agent configuration passes. Use --no-javascript-evaluation when inspecting untrusted pages, enable source maps only when needed for a large site, and restrict filesystem roots to the project. Add a heap-snapshot check to performance work on long-lived pages, and test keyboard access after UI changes. If you maintain an agent integration, pin the MCP version and record which tools are enabled rather than accepting the defaults silently.

Sources

Related games

Keep reading

GitHub Copilot Fusion routes each coding task across multiple models

Copilot Automations can now be shared, billed and owned by a repository

Cloudflare open-sources Void to connect Vite apps to Workers

GitHub Copilot arrives in JetBrains Air with local and cloud agents

Node.js 27 alpha lands V8 15.6 with new memory defaults

Node.js schedules high-severity security releases for 11 November

OpenAI updates its Model Spec around five behavioural values

Claude Opus 5.5 targets agentic coding at a lower cost per task

Godot 4.8 beta 2 fixes regressions and raises the .NET floor

All creator news →