Human and scripted diagnostics
Inspector & CLI
Use the same diagnostics surface from a visual tool or a terminal.
Explore source ↗Capability
Inspector controls, shared view models, WYSIWYG tools, a desktop client, in-process diagnostics, and CLI commands provide multiple ways to work with CDP targets.
- 01
Desktop inspector composition
- 02
WYSIWYG overlays and editing
- 03
In-process diagnostic tools
- 04
Scriptable CLI client
How it composes
From intent
to working system.
Connect
Clients discover targets and create a protocol session.
Model
Shared view models normalize trees, properties, events, and commands.
Present
Controls and WYSIWYG packages compose a visual inspector.
Script
CLI commands expose the same session to terminals and agents.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
dotnet tool install --global Chrome.DevTools.Cli --prereleasecdp-inspector targets --url http://localhost:9222cdp-inspector tree --target 0cdp-inspector screenshot --target 0 --output app.pngModules in this capability
Use one layer.
Compose the rest.
Reusable inspector client controls.
↗02Chrome.DevTools.Inspector.SharedShared inspector models and UI composition.
↗03Chrome.DevTools.Inspector.WysiwygVisual designer and overlay tools.
↗04Chrome.DevTools.CliCDP inspector command-line client.
↗05Chrome.DevTools.DiagnosticToolsIn-process diagnostic inspector integration.
↗Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.