Chrome DevTools Protocol core
Protocol Server
Speak a standard diagnostics protocol before choosing a UI framework.
Explore source ↗Capability
A framework-neutral CDP server, session router, domain model, HTTP discovery endpoint, and WebSocket transport for exposing native application targets.
- 01
HTTP target discovery
- 02
WebSocket sessions
- 03
Commands and domain events
- 04
Framework-neutral server core
How it composes
From intent
to working system.
Target
Applications publish inspectable runtime targets.
Session
WebSocket connections isolate command and event streams.
Domain
Handlers implement DOM, Runtime, CSS, Input, Page, and related protocol areas.
Adapter
Framework packages translate domain operations into native UI behavior.
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 add package Chrome.DevTools.Protocol --prerelease<PackageReference Include="Chrome.DevTools.Protocol" Version="VERSION" /><PackageVersion Include="Chrome.DevTools.Protocol" Version="VERSION" />var server = new CdpServer(new CdpServerOptions{ Port = 9222});
await server.StartAsync(cancellationToken);Modules in this capability
Use one layer.
Compose the rest.
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.