Pimp My IDE / garage dispatchBack to the garage
October 8, 2026 / browser agents / authority

A browser tool needs an ignition map.

Chrome DevTools for agents can inspect a page, run JavaScript, cross navigation boundaries, and write files. Give each power its own switch before the browser opens.

Start with observation. Open execution on purpose.
BROWSER AUTHORITY / LIVE SCOPECONFIG ONLY
LOCKED
READ
PAGERUN
SCRIPTCROSS
PATHWRITE
FILE

Inspection and execution are different jobs.

Chrome's October DevTools recap adds controls for coding agents that use Chrome DevTools MCP. The server can now disable JavaScript evaluation across the evaluation tools, initialization scripts, and navigations to javascript:, data:, or vbscript: URLs.[1][2]

That gives review work a narrower mode. An agent can still read a page, inspect the document, collect console output, and study network behavior without receiving a general script-execution route. Read-only is not a complete browser sandbox, but it is a concrete reduction in authority.

Do not grant script execution because the task happens inside a browser.

File reach needs a named root.

The current configuration reference says file-writing tools use the operating system temporary directory when the client does not negotiate MCP roots. The --filesystemRoot option can name one or more allowed directories. The --allowUnrestrictedPaths switch removes that default restriction and is off by default.[2]

Chrome's recap describes unrestricted paths as a CLI default. That sentence conflicts with the current repository documentation and the package help for version 1.10.1. Treat the running package and its exact configuration as the operational source. Record the disagreement instead of smoothing it away.[1][3]

Source maps trade memory for names.

Source maps can turn generated stack frames into application filenames and symbols. They can also consume substantial memory on a large site. The new --no-source-maps option lets an operator start without them and enable deeper source inspection only when the task needs it.[1][2]

Keep this switch out of the security column. Disabling source maps changes diagnostic depth and memory use. It does not stop network access, script execution, file navigation, or file writes.

The browser profile is part of the boundary.

The repository warns that an MCP client can inspect, debug, and modify data in the connected browser. It tells users not to expose sensitive or personal information they do not want the client to receive. Performance tools may also send trace URLs to the Chrome User Experience Report API unless --no-performance-crux is set. Usage statistics have a separate opt-out.[3]

Use a disposable browser profile for agent work. Log out of unrelated services. Keep trace sharing, usage statistics, network-header redaction, and JavaScript execution as separate receipt fields. One private window badge cannot describe all four.

Interactive makeover / vague browser access replaced

Set the browser breaker.

This replaces one broad "browser tools on" setting with an operating mode, four explicit interlocks, and a copyable launch card. It is better because execution, navigation, file reach, and data handling stay visible as separate decisions. This component drafts configuration. It does not start Chrome or change an MCP client.

PurposeExecutionFile reachReceipt

Ignition mode

Choose the narrowest mode that can finish the task. Then select the interlocks to include in the launch card.

Operating mode
Launch-card interlocks
Launch card / structure only

Browser authority receipt

OBSERVE / JAVASCRIPT EVALUATION OFFThe card requests page inspection without opening the general evaluation route.
0 interlocks selectedSelect the fields this card should request. No live browser, profile, root, or trace evidence is attached.
Sources read / October 8, 2026

Source log

Open the evidence boundary
  1. Chrome for Developers, "New in DevTools - October 2026", published September 22 and read October 8, 2026. Google documents JavaScript execution controls, optional source maps, configurable filesystem roots, heap inspection, Progressive Web App tools, and other Chrome 153 and 154 changes.
  2. Chrome DevTools MCP configuration at commit 2744afa, read October 8, 2026. The reference defines JavaScript evaluation, file navigation, source-map, header-redaction, filesystem-root, and unrestricted-path behavior and defaults.
  3. Chrome DevTools MCP README at commit 2744afa, read October 8, 2026. The repository documents browser-data exposure, Chrome support, Chrome User Experience Report trace lookups, usage statistics, isolated mode, and the smaller slim tool set.
  4. Chrome DevTools MCP changelog at commit 2744afa, read October 8, 2026. The changelog ties the expanded no-evaluation behavior, source-map option, and filesystem roots to their implementation commits.

Artifact check: we resolved chrome-devtools-mcp 1.10.1 from npm and ran its help command in a disposable home and cache. The help output confirmed the JavaScript evaluation, source-map, filesystem-root, unrestricted-path, and network-header options. We did not connect the server to Chrome, inspect a live page, or test containment. The breaker drafts a launch request. It does not report that a browser session is safe.