GPAL
  • Concepts
  • Tutorials
  • Library
  • Endpoints
  • API
  • OttoMagic
  • Services
v1.0.0
Library
  • AI
  • Application
  • Base64Helper
  • Browser
  • Converter
  • Credentials
  • Database
  • Excel
  • File
  • Form
  • Gherkin
  • GoogleDorking
  • GoogleDrive
  • GoogleSheets
  • Grid
  • ImageHelper
  • Launcher
  • Logger
  • Mail
  • PuppeteerClient
  • RESTClient
  • Selector
  • Url

PuppeteerClient

  • Executing CDP Commands via PuppeteerClient
  • PuppeteerClient - In-Process CDP Automation
  • PuppeteerCommunicator - The CDP Transport Layer

Library

Executing CDP Commands via PuppeteerClient

PuppeteerClient mirrors RESTClient's Execute family - Execute(), Execute<T>(), ExecuteAsync(), AndThen() - plus navigation, element interaction, and DOM query methods backed directly by CDP. All of it runs on GPAL's own custom CDP implementation, not a Puppeteer-library wrapper.

PuppeteerClient - In-Process CDP Automation

PuppeteerClient is the in-process equivalent of RESTClient - the same fluent endpoint-based API, but commands are sent directly over a Chrome DevTools Protocol (CDP) connection instead of through the OttoMagic REST API.

PuppeteerCommunicator - The CDP Transport Layer

PuppeteerCommunicator is the lowest-level layer in GPAL's browser stack - a managed websocket connection that speaks the Chrome DevTools Protocol directly, used internally by PuppeteerClient and the Puppeteer-based automation engines.

On this page


Library
Executing CDP Commands via PuppeteerClient
PuppeteerClient - In-Process CDP Automation
PuppeteerCommunicator - The CDP Transport Layer

GPAL

Generally Positive Automation Library

Get Started Library Desktop Viewer

Learn More

Contact Us

GPAL License

About GPAL

FAQs


Bug Reports

Report a bug


Software Decisions Inc © 2026 Copyright
X