Skip to content

feat: memory debugging tools#2169

Merged
Lightning00Blade merged 2 commits into
mainfrom
enable-memeory-tooling
Jun 5, 2026
Merged

feat: memory debugging tools#2169
Lightning00Blade merged 2 commits into
mainfrom
enable-memeory-tooling

Conversation

@Lightning00Blade

@Lightning00Blade Lightning00Blade commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

Updates the flag for the memory tooling to remove the experimental bit (keep alias for backwards compatibility).
And updates the SKILLs to reflected the update names and point to the available tools.

Q: Should it be called take_heapsnapshot or take_heap_snapshot?

@nroscino nroscino left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@Lightning00Blade Lightning00Blade marked this pull request as ready for review June 3, 2026 09:56
@Lightning00Blade Lightning00Blade requested a review from devnook June 3, 2026 09:56
@Lightning00Blade Lightning00Blade force-pushed the enable-memeory-tooling branch from 131c6e9 to dd2c12b Compare June 5, 2026 13:12
@Lightning00Blade Lightning00Blade added this pull request to the merge queue Jun 5, 2026
Merged via the queue into main with commit 0217397 Jun 5, 2026
21 checks passed
@Lightning00Blade Lightning00Blade deleted the enable-memeory-tooling branch June 5, 2026 13:24
@ranieleda-ui

ranieleda-ui commented Jun 5, 2026 via email

Copy link
Copy Markdown

pull Bot pushed a commit to CrazyForks/chrome-devtools-mcp that referenced this pull request Jun 8, 2026
🤖 I have created a release *beep* *boop*
---


##
[1.2.0](ChromeDevTools/chrome-devtools-mcp@chrome-devtools-mcp-v1.1.1...chrome-devtools-mcp-v1.2.0)
(2026-06-08)


### 🎉 Features

* add experimental TOON support for structured content output
([ChromeDevTools#2042](ChromeDevTools#2042))
([aa33bff](ChromeDevTools@aa33bff))
* Adds close_heapsnapshot MCP tool
([ChromeDevTools#2174](ChromeDevTools#2174))
([8713b93](ChromeDevTools@8713b93))
* Handle multiple providers of third-party developer tools
([ChromeDevTools#2168](ChromeDevTools#2168))
([30d59a7](ChromeDevTools@30d59a7))
* implement extension service worker logs
([ChromeDevTools#1915](ChromeDevTools#1915))
([29e3898](ChromeDevTools@29e3898))
* memory debugging tools
([ChromeDevTools#2169](ChromeDevTools#2169))
([0217397](ChromeDevTools@0217397))
* support allowedUrlPattern & blockedUrlPattern Options
([ChromeDevTools#2037](ChromeDevTools#2037))
([02b4492](ChromeDevTools@02b4492))


### 🛠️ Fixes

* Cursor plugin homepage setting field
([ChromeDevTools#2173](ChromeDevTools#2173))
([8971890](ChromeDevTools@8971890))


### 📄 Documentation

* **skill:** guide agent to prompt for --categoryExtensions
([ChromeDevTools#2189](ChromeDevTools#2189))
([8b458f7](ChromeDevTools@8b458f7))


### ⚡ Performance

* lighthouse file saves to run concurrently
([ChromeDevTools#2178](ChromeDevTools#2178))
([f90f863](ChromeDevTools@f90f863))


### 🏗️ Refactor

* change type of logger
([ChromeDevTools#2165](ChromeDevTools#2165))
([bf0574d](ChromeDevTools@bf0574d))
* use validate files on the tool level
([ChromeDevTools#2152](ChromeDevTools#2152))
([2e039c0](ChromeDevTools@2e039c0)),
closes
[ChromeDevTools#2150](ChromeDevTools#2150)

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants