fix: paginate page 0 in list_network_requests and list_console_messages - #2359

Merged

OrKoN merged 2 commits into

ChromeDevTools:mainfrom

serhiizghama:fix/paginate-page-index-zero

Jul 14, 2026

serhiizghama commented Jul 14, 2026

Contributor

list_network_requests and list_console_messages treat an explicit pageIdx: 0 as "no pagination" and dump every result, while pageIdx: 1 and up paginate correctly.

The guards in setIncludeNetworkRequests/setIncludeConsoleData build the pagination options with options?.pageSize || options?.pageIdx, so a bare {pageIdx: 0} collapses to undefined — 0 is falsy — and paginate() never runs. That's a bit odd since paginate() already decides for itself when there's nothing to paginate (noPaginationOptions checks pageSize === undefined && pageIdx === undefined), so page 0 is a perfectly valid first page there. The memory tools, which pass their options straight through to paginate(), handle pageIdx: 0 fine — only these two guards get it wrong, so an agent walking pages 0, 1, 2… gets the full list on page 0 and a 20-item window from page 1 on.

Switched both guards to an explicit !== undefined check so pageIdx: 0 reaches paginate() and gets the default page size like every other page. Both-omitted still short-circuits to the full list, so nothing else changes. Added a regression test for the {pageIdx: 0} case.

serhiizghama added 2 commits

July 14, 2026 09:24


          fix(pagination): treat pageIdx 0 as a valid page in network and conso…

c698231

…le lists

The pagination guard used a truthiness check, so an explicit pageIdx: 0
collapsed to no pagination and returned every result, while pageIdx: 1 and
up paginated. paginate() already gates on both options being undefined, so
page 0 is a valid first page there. Use an explicit undefined check so it
reaches paginate() and gets the default page size.


          test: cover pageIdx 0 without pageSize for network pagination

2542c96

OrKoN approved these changes

View reviewed changes

OrKoN left a comment

Collaborator

Thanks!

OrKoN enabled auto-merge

July 14, 2026 06:06

OrKoN added this pull request to the merge queue

Merged via the queue into ChromeDevTools:main with commit d0025b3

19 checks passed

browser-automation-bot mentioned this pull request

chore(main): release chrome-devtools-mcp 1.6.0 #2306

Merged

kku1993 pushed a commit to kku1993/chrome-devtools-mcp that referenced this pull request


          chore(main): release chrome-devtools-mcp 1.6.0 (ChromeDevTools#2306)

f621d00

🤖 I have created a release *beep* *boop*
---


##
[1.6.0](ChromeDevTools/chrome-devtools-mcp@chrome-devtools-mcp-v1.5.0...chrome-devtools-mcp-v1.6.0)
(2026-07-14)


### 🎉 Features

* add experimentalGcfFormat flag for GCF-encoded tool responses
([ChromeDevTools#2235](ChromeDevTools#2235))
([3d21389](ChromeDevTools@3d21389))
* Print object count and total sizes in get_heapsnapshot_details
([ChromeDevTools#2325](ChromeDevTools#2325))
([15a6b78](ChromeDevTools@15a6b78))
* support --allow-unrestricted-paths configuration
([ChromeDevTools#2296](ChromeDevTools#2296))
([6e56c02](ChromeDevTools@6e56c02))
* Support filter with heap snapshots aggregates
([ChromeDevTools#2323](ChromeDevTools#2323))
([2812902](ChromeDevTools@2812902))
* update Lighthouse to 13.4.0
([ChromeDevTools#2317](ChromeDevTools#2317))
([ffc6060](ChromeDevTools@ffc6060))


### 🛠️ Fixes

* enforce .gz instead of json.gz in performance tools
([ChromeDevTools#2305](ChromeDevTools#2305))
([b06e39b](ChromeDevTools@b06e39b))
* keep a still-open selected page instead of falling back to the first
page
([ChromeDevTools#2328](ChromeDevTools#2328))
([c645eee](ChromeDevTools@c645eee)),
closes
[ChromeDevTools#2304](ChromeDevTools#2304)
* keep page ids unique across browser reconnects
([ChromeDevTools#2345](ChromeDevTools#2345))
([3e8d922](ChromeDevTools@3e8d922))
* paginate page 0 in list_network_requests and list_console_messages
([ChromeDevTools#2359](ChromeDevTools#2359))
([d0025b3](ChromeDevTools@d0025b3))
* release held modifiers when press_key key event fails
([ChromeDevTools#2347](ChromeDevTools#2347))
([78ccb19](ChromeDevTools@78ccb19))
* report when the selected page was auto-replaced by the fallback
([ChromeDevTools#2308](ChromeDevTools#2308))
([2c16ac3](ChromeDevTools@2c16ac3)),
closes
[ChromeDevTools#2304](ChromeDevTools#2304)
* resolve page ids only among listed pages
([ChromeDevTools#2332](ChromeDevTools#2332))
([eb04951](ChromeDevTools@eb04951)),
closes
[ChromeDevTools#2304](ChromeDevTools#2304)
* **snapshot:** resolve element ids on the correct snapshot
([ChromeDevTools#2295](ChromeDevTools#2295))
([b703f2c](ChromeDevTools@b703f2c))
* **telemetry:** resolve enum values through nested schema wrappers
([ChromeDevTools#2315](ChromeDevTools#2315))
([c065fd9](ChromeDevTools@c065fd9))
* Wait until daemon is started
([ChromeDevTools#2327](ChromeDevTools#2327))
([ed7e95d](ChromeDevTools@ed7e95d))


### 📄 Documentation

* add Grok Build CLI configuration section
([ChromeDevTools#2294](ChromeDevTools#2294))
([aa4be07](ChromeDevTools@aa4be07))
* update memory leak debugging skill
([ChromeDevTools#2330](ChromeDevTools#2330))
([c1736a0](ChromeDevTools@c1736a0))


### ⚡ Performance

* concurrent I/O in Root Path Resolution
([ChromeDevTools#2279](ChromeDevTools#2279))
([b2c63e6](ChromeDevTools@b2c63e6))


### 🏗️ Refactor

* clean up McpContext getters
([ChromeDevTools#2340](ChromeDevTools#2340))
([5b33deb](ChromeDevTools@5b33deb))
* clean up more of the context interface
([ChromeDevTools#2335](ChromeDevTools#2335))
([9cd734b](ChromeDevTools@9cd734b))
* clean up page management
([ChromeDevTools#2333](ChromeDevTools#2333))
([16db01f](ChromeDevTools@16db01f))
* clean up page snapshot generation
([ChromeDevTools#2348](ChromeDevTools#2348))
([68cfce2](ChromeDevTools@68cfce2))
* make collectors work per page
([ChromeDevTools#2324](ChromeDevTools#2324))
([9bc61b4](ChromeDevTools@9bc61b4))
* move and rename files
([ChromeDevTools#2355](ChromeDevTools#2355))
([9c3542b](ChromeDevTools@9c3542b))
* move DevTools universe to McpPage
([ChromeDevTools#2341](ChromeDevTools#2341))
([c006c9b](ChromeDevTools@c006c9b))
* move remaining McpContext getters
([ChromeDevTools#2342](ChromeDevTools#2342))
([58ba174](ChromeDevTools@58ba174))
* remove isolated context getter
([ChromeDevTools#2336](ChromeDevTools#2336))
([8a4ddb3](ChromeDevTools@8a4ddb3))
* Use array instead of Map for idToClassKey
([ChromeDevTools#2321](ChromeDevTools#2321))
([ff53b7b](ChromeDevTools@ff53b7b))
* use helper for Dialog handle
([ChromeDevTools#2334](ChromeDevTools#2334))
([64005f9](ChromeDevTools@64005f9))
* use response page in formatting
([ChromeDevTools#2349](ChromeDevTools#2349))
([c53c1ec](ChromeDevTools@c53c1ec))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

triuzzi mentioned this pull request

chore: sync upstream chrome-devtools-mcp v1.6.0 triuzzi/brave-devtools-mcp#22

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet