d886968863
[Prototype] Heapsnapshot diff tool
2026-05-20 12:57:14 +02:00
b2b05a0670
chore(memory): expose retainer logic ( #2056 )
...
Allows the LLM to query the heapsnapshot further to understand what the
retainer path logic.
2026-05-18 09:54:00 +00:00
9f5dd6229c
chore(memory): expose way to get the nodes ( #1916 )
...
The next step for the memory debugging is to provide the nodes that the
aggregates have, from which you can get the retainers of the object.
2026-04-23 09:44:06 +00:00
9211c6b52d
chore(memory): expose a tool for getting the inital data. ( #1909 )
...
This refactors the code to extract the Id logic from the PageCollector
and provide it in the heapsnapshot.
We need to use an UID as we need the internal ClassKey to query the
heapsnapshot, but that is a strange string (usually looking like
`,ClassName`) which may get the LLM confused as we use comma separated
output.
2026-04-20 18:39:48 +00:00
0331f6a8a2
chore: implement memory snapshot information ( #1874 )
...
WIP of exposing a tool for debugging memory issue directly with the MCP
2026-04-17 12:40:41 +00:00
302e5a0419
refactor: consistently use McpPage in tools ( #1057 )
...
Follow-up to
https://github.com/ChromeDevTools/chrome-devtools-mcp/commit/caf601a32832bb87cfac801a6bbeacb87508412f
The work is not complete and as a follow-up I will handle other Context
methods and moved whatever is relevant to the McpPage. Also, duplicate
getters would go away.
2026-02-27 09:41:08 +00:00
5f694c60ff
refactor: improve type safety for page scoped tools ( #1051 )
...
I think we should create proper classes for tool definitions soon.
Follow-up for
https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/1022
2026-02-26 14:33:57 +00:00
7ffdc5ee4d
feat: add take_memory_snapshot tool ( #1023 )
...
Refs: https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/406
2026-02-23 18:12:29 +00:00
Nikolay Vitkov