Skip to main content
skill CX Codex

inspect-in-devtools — Claude Code skill: debugging and setup

inspect-in-devtools is a Claude Code skill that connects an agent to the Chrome DevTools interface. It reveals page targets, reads the current selection, and handles DevTools comment threads.

Apache-2.0 119 installs ★ 58,707 updated 2026-10-23

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add ChromeDevTools/chrome-devtools-mcp --skill inspect-in-devtools -a claude-code
Open on GitHub

What inspect-in-devtools does

inspect-in-devtools opens DevTools for a page and can reveal a panel, a DOM element, or a network request. It also reads the element or request currently selected by the user. For DOM targets, the workflow can use a page snapshot and tools for CSS inspection, screenshots, or script evaluation.

The skill fetches DevTools comment threads, answers questions or applies requested fixes, then resolves the threads. In watch mode, it checks again after 10 seconds and stops after 12 consecutive empty polls. It requires Chrome M159 or later running with a visible browser window, the --devtools-comments flag in the MCP server configuration, and a pageId from list_pages or new_page. Without the flag, the DevTools reveal and comment tools are unavailable.

What it helps with

  • reveal a selected DOM element in the Elements panel
  • show a network request in the Network panel
  • inspect the request selected in DevTools
  • answer DevTools comments and resolve their threads

Example prompts for the agent

  • Show the page element I selected in DevTools.
  • Open the request related to this error in the Network panel.
  • Review the DevTools comments, apply the requested fixes, and resolve the threads.

How to install inspect-in-devtools

1Skills CLI (Vercel)

npx skills add ChromeDevTools/chrome-devtools-mcp --skill inspect-in-devtools -a claude-code

2Manually: put the files in place

~/.claude/skills/inspect-in-devtools/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/inspect-in-devtools/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about inspect-in-devtools

How do I install inspect-in-devtools in Claude Code?

Run npx skills add ChromeDevTools/chrome-devtools-mcp --skill inspect-in-devtools -a claude-code. The skill file is at ~/.claude/skills/inspect-in-devtools/SKILL.md.

What does inspect-in-devtools do?

It connects an agent to the Chrome DevTools interface to reveal panels, DOM elements, and network requests, inspect the current selection, and handle comment threads.

What does inspect-in-devtools need to run?

It needs Chrome M159 or later outside --headless mode, the --devtools-comments flag in the MCP server configuration, and a pageId from list_pages or new_page.

Source text

SKILL.md · Apache-2.0
---
name: inspect-in-devtools
description: Use this skill to connect to the Chrome DevTools UI for interactive debugging, UI/UX review, Q&A, showing elements/network requests/panels to the user, inspecting the user's current DevTools selection, and addressing or polling for DevTools UI comment threads.
---

# Debug, Review, and Q&A in DevTools

Use this skill to:

1. **Show a target to the user**: Open DevTools and reveal a panel, a DOM element, or a network request.
2. **Inspect the user's selection**: Read the element or network request that the user selected in DevTools.
3. **Address DevTools comments**: Fetch comment threads, answer questions or apply fixes, and resolve the threads.

## Prerequisites

- **Chrome version**: Chrome M159 or later.
- **Required flag**: `--devtools-comments` in the MCP server config. Without it, `open_devtools`, `reveal_in_devtools`, `get_devtools_comments`, and `resolve_devtools_comment` are not available.
- **Headed browser**: Chrome must not run in `--headless` mode.
- **Page targeting**: All tools require a `pageId` from `list_pages` or `new_page`.

## Workflows

### 1. Open DevTools

Call `open_devtools` with `pageId`. Do this before you call `reveal_in_devtools`, `get_devtools_comments`, or `resolve_devtools_comment`.

### 2. Reveal a panel, element, or network request

Call `reveal_in_devtools` with `pageId` and these optional parameters:

- `panelName`: `"elements"`, `"network"`, `"sources"`, or `"console"`. Pass it alone to switch panels.
- `uid`: Element `uid` from `take_snapshot`. Reveals the element in the Elements panel.
- `reqid`: Request `reqid` from `list_network_requests`. Reveals the request in the Network panel.

`uid` and `reqid` are mutually exclusive.

### 3. Inspect the user's selection

- **DOM element**: Call `take_snapshot`. The snapshot marks the element selected in the Elements panel. Pass its `uid` to `get_css_styles`, `take_screenshot`, or `evaluate_script`.
- **Network request**: Call `get_network_request` and omit `reqid`. It returns the request selected in the Network panel.

### 4. Handle comment threads

Select the mode from the user's request.

#### Mode A: One-shot (comments already exist)

Use this mode when the user says the comments are already in DevTools, or asks you not to poll.

1. Call `get_devtools_comments` once.
2. Process and resolve each returned thread.
3. Summarize your changes and answers in chat, then end your turn. Do **not** poll.

#### Mode B: Watch (wait for user feedback)

Use this mode when the user asks you to wait while they debug, review, or add comments.

1. Call `get_devtools_comments` immediately.
2. While the result is `"No open DevTools comments found."`, wait 10 seconds, then call it again. Call it immediately if a `"DevTools comment threads updated"` notification arrives.
3. Stop after 12 consecutive empty polls (about 2 minutes) or when the user asks you to stop.
4. When threads appear, process and resolve them. Then reset the empty-poll counter and continue polling.

Rules for polling:

- **Use a background sub-agent** when sub-agent tools are available, so the main thread stays responsive. The sub-agent returns the threads to the main agent, or resolves them itself if it has workspace and MCP tools.
- **Poll inline** only when sub-agent tools are unavailable. Do not end your turn early.
- **Never call `get_devtools_comments` back-to-back** without the 10-second delay.

#### Process and resolve a thread

For each `### Thread: <id>`:

1. **Inspect the anchored target**:
   - `Related element uid`: Use `get_css_styles`, `take_snapshot`, or `take_screenshot` with the `uid`.
   - `Related network reqid`: Use `get_network_request` with the `reqid`.
   - Optionally call `reveal_in_devtools` to show the target to the user.
2. **Address the comment**:
   - For a code or styling request, apply the fix in the workspace. Reload and verify the page if needed.
   - For a question or root-cause investigation, collect diagnostic data. Do not make unnecessary code edits.
3. **Resolve**: Call `resolve_devtools_comment` with `pageId`, `threadId`, and `replyText`:
   - For a question or root cause, write a detailed answer.
   - For a straightforward fix, write 1–2 sentences that state the change and the file.

© ChromeDevTools · Apache-2.0 · ChromeDevTools/chrome-devtools-mcp

Similar skills

All skills for Browser and scraping →

From the same set9

chrome-devtools This skill connects Chrome DevTools through MCP for page debugging, browser automation, performance checks, and network inspection. CX Codex +1 9,400installs chrome-devtools-cli Automates browser tasks via the chrome-devtools CLI. Handles page navigation, element clicks, text input, and performance profiling. CX Codex +1 8,800installs debug-optimize-lcp debug-optimize-lcp breaks Largest Contentful Paint into four sequential stages and shows exactly where the main content load is bottlenecked. CX Codex +1 4,100installs a11y-debugging a11y-debugging audits web-page accessibility with Chrome DevTools MCP, covering semantics, ARIA, focus states, keyboard navigation, tap targets and contrast. CX Codex +1 4,100installs memory-leak-debugging memory-leak-debugging finds memory leaks in JavaScript and Node.js with Chrome DevTools MCP. Use it to investigate high memory use, OOM errors, and heap snapshots. CX Codex +1 3,700installs troubleshooting troubleshooting diagnoses connection failures and tool errors in Chrome DevTools MCP step by step. Helpful when the server refuses to launch or tab commands fail. CX Codex +1 3,600installs cookie-debugging cookie-debugging — a skill for inspecting cookies, sessions, and authentication errors via Chrome DevTools MCP. Diagnoses 401/403, auth redirects, Set-Cookie issues, and verifies cookie consent compliance. CX Codex +1 1,200installs chrome-devtools-mcp chrome-devtools-mcp connects a live Chrome browser to your coding agent via MCP to record performance traces, inspect network calls, and automate browser tasks. ★ 58,707repo stars

Project sponsors

Companies that keep this analytics open