ChromeDevTools / ChromeDevTools/chrome-devtools-mcp

Network requests happening before the --autoconnect handshake happened are not showing up in get_network_request

Open
#1,036 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

collecting-feedback feature
Dominant language
TypeScript
Stars
52.3k
Forks
4.3k
Avg merge
2d 7h
Merged PRs (30d)
83

Description

Description of the bug
  • human opens devtools and selects a network request in there
  • AI agent is using --autoconnect
  • Human prompts with something like " tell me what you know about the network request I have selected in chrome devtools" in their AI agent
  • AI agent will start --autoconnect handshake, which the human accepts
  • tool get_network_request is called and returns empty

It makes sense that this happens, as the MCP server has no access to network requests that happened before its initialization and connection with Chrome. It's frustrating though, so maybe we can document this somehow?

Reproduction

No response

Expectation

No response

MCP configuration

using gemini cli with gemini 2.5.

Chrome DevTools MCP version

0.17.0

Chrome version

No response

Coding agent version

No response

Model version

No response

Chat log

No response

Node version

No response

Operating system

None

Extra checklist
  • I want to provide a PR to fix this bug

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named in the issue. Start by reviewing the documentation for --autoconnect and get_network_request, then document that requests made before the handshake are unavailable to the MCP server; done means this limitation and its timing are clearly explained.

Written by the indexing model from the issue text.

Assessment

Domain
devtools, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.