Skip to content

extension_inspect ​

Inspect a web page (or targetId) over the debugger protocol: HTML, DOM, console, probes, closed shadow roots.

Quick start ​

Read the DOM the content script injected on the cart page, shadow roots included

Asked what the content script injected, the agent runs the extension and reads the page DOM.

Asked what the content script injected, the agent runs the extension and reads the page DOM.

How the agent uses it ​

Surfaces by name are extension_dom_snapshot. Firefox: agent bridge, needs allowEval:true.

Page text in the answer ​

Part of this tool's answer is text a web page or the extension wrote. The server fences it between <untrusted-data-ID> and </untrusted-data-ID> with a fresh random ID per call, named in untrusted.boundary. A fence is a signal to the model, not a gate: pair it with --no-ship when the agent reads pages you do not trust. See Server flags and telemetry.

Reference ​

Grouplocal, on by default
TierSee
Needsa live dev or start session
Read onlyno
Destructiveno
Idempotentyes
Reaches the open webno

Inputs ​

InputTypeRequiredDefaultWhat it does
projectPathstringyesProject root of a running session: extension_dev, extension_start, or npx extension dev|start by hand
urlstringnoNavigate here first, or the url substring to pick.
targetIdstringnoA page's targetId (extension_open, or dom_snapshot listTargets); overrides url.
probearray of stringnoCSS selectors to count and sample.
includearray of "html" | "summary" | "meta" | "dom_snapshot" | "console" | "extension_roots"no["summary","meta","console"]What to include
browserstringnoSession browser; required when several run.
maxBytesnumberno262144HTML byte cap (0 = none).
deepDombooleannofalsePierce closed shadow roots; other open roots are not crossed.

When it fails ​

Next ​

  • MCP server: install, the two groups and the session gates
  • Install in your client
  • extension_analyze: Analyze a BUILT extension in dist/<browser>: sizes, entries, permissions, store checks (not on a dev build).
  • extension_doctor: Diagnose a dev session leg by leg, each with its remediation; run it first when an act tool errors unexpectedly.
  • extension_dom_snapshot: Take a shallow DOM snapshot of one open surface or targetId, or list what is open (listTargets on the debug port, listTabs).
  • extension_list_extensions: List the extensions in a session's browser; its own carries ownExtension:true.
  • extension_logs: Read a dev session's logs from every context in one timeline, or follow:true for live frames after the replayed ring.
  • extension_manifest_validate: Validate a manifest.json across browsers; buildBlocking lists the errors that make extension_build refuse.
  • extension_screenshot: Take a .png of one open surface, page or targetId in a live session (Safari: pages only); open it with extension_open first.
  • extension_theme_verify: Verify a Chrome theme manifest headless: the colors Chrome would paint and the keys it discards.