Pimp My IDE / garage dispatchBack to the garage
October 11, 2026 / browser agents / network scope

Give the browser a fenced route.

A disposable profile helps. A named origin, a smaller tool set, and blocked side routes tell you what the browser agent can reach.

Choose the destination before turning the key.
PERIMETER SELECTORPLAN ONLY
https://staging.example.test/*
INPUTOPEN?
NAVIGATIONOPEN?
NETWORKOPEN?
DEBUGGINGOPEN?
ORIGIN AND TOOL ROUTEUNSET

A clean profile is not a network boundary.

Chrome DevTools for agents can open pages, inspect a live browser, emulate devices, run audits, and debug code. Chrome's setup guide warns that the agent can read and modify data in the connected browser. It can act on your behalf when that browser already has an authenticated session.[1]

The --isolated option creates a temporary user data directory and removes it when the browser closes. That separates browser state. It does not say which hosts the browser may contact. Profile isolation and destination control solve different problems.[2]

Temporary cookies do not make an unlimited network route narrow.

Start with one allowed origin.

The current configuration reference has --allowed-url-pattern. On Chrome 149 or newer, it lets the server attach only to allowed targets and blocks unallowed navigations and subresources. The same reference warns that regular-expression groups are rejected because they are not enforced on redirects or subresources. Use an exact value or a simple wildcard.[2]

An allowlist is stronger than a pile of guessed block patterns for a bounded staging test. Keep authentication, redirects, content-delivery hosts, and API calls in view. If the page needs four origins, name four origins. Do not turn the rule into * to make the console quiet.

Remove tools the job does not need.

The server exposes switches for input, navigation, emulation, performance, network, debugging, and memory tool categories. Most are on by default. Experimental page-provided tools, WebMCP tools, extension tools, and Progressive Web App tools default off.[2]

A layout inspection may need navigation and screenshots but not input. A performance pass may need navigation, performance, and network tools but not extension automation. The category switches do not prove safety. They do make the granted tool set reviewable.

Keep observation routes separate.

Performance traces can send inspected URLs to the Chrome User Experience Report API unless --performance-crux=false is set. Usage statistics have a separate opt-out. Network-header redaction is also separate and defaults off.[2]

Put those choices in the launch card. A person reviewing the job should not have to infer whether a target URL, tool-use record, or network header can leave the local session.

Interactive makeover / broad browser toggle replaced

Set the perimeter.

This replaces a single browser-tools switch with one origin field and four circuit selectors. It drafts a review card. It does not launch Chrome, test redirects, confirm authentication, or prove containment.

DestinationTool setObservationReview card

Route controls

Enter the staging origin. Select only the tool categories the task needs.

Use one exact host or a simple wildcard pattern. Add required origins to the real configuration one by one.

Required tool categories
Perimeter card / structure only

Browser route receipt

1 tool category selectedThe route has an origin and one selected tool category. Review is still required.
Sources read / October 11, 2026

Source log

Open the evidence boundary
  1. Chrome for Developers, "Get started with Chrome DevTools for agents", updated May 13 and read October 11, 2026. The guide describes the MCP server, CLI, agent skills, browser access, and the risk of connecting an agent to an authenticated browser.
  2. Chrome DevTools MCP configuration at commit f08dbe1, committed October 9 and read October 11, 2026. The reference defines category switches, isolated profiles, allowed URL patterns, trace lookups, usage statistics, JavaScript evaluation, file navigation, and network-header redaction.
  3. Chrome for Developers, "Streamline your AI coding workflow with Chrome DevTools for agents 1.0", published May 19 and read October 11, 2026. The release post covers Lighthouse, emulation, extension debugging, WebMCP, memory analysis, and authenticated-session handoff.

Source boundary: these are Chrome project sources. They document intended behavior and current options. This article did not connect the package to a browser or test that the allowed-origin rule contains every redirect and subresource path in a real application. The selector produces a review card, not a safety verdict.