A browser automation interface showing CDP commands and a live page preview

04 / 06 — Automation Tooling

A browser driven over raw CDP — for pages that fight back.

Client
Personal project
Year
2026
Role
Engineering
Stack
Node.js · Chromium · Chrome DevTools Protocol · WebSockets

Overview

Pilot drives a real Chromium instance over a raw Chrome DevTools Protocol WebSocket, with no framework sitting in between to give it away.

Pilot Browser interface — CDP command log and live page preview
Fig. 1Raw CDP. No framework in between.

01 — The challenge

Standard browser automation goes through Puppeteer or Playwright. They connect in a way sites can detect — enabling CDP domains that monitoring systems watch for, and leaving artefacts in the page. Anything protected spots them immediately.

02 — The solution

Pilot sends only what it needs and nothing more, which is the single design choice that makes it work where other tools get blocked. On top of that it exposes navigation, clicking, typing, scrolling, arbitrary JavaScript evaluation, screenshots, tab management, and a record-and-replay layer for repeatable workflows.

0

Framework fingerprints

1

WebSocket connection

100%

Raw CDP control

Pilot Browser record-and-replay timeline showing captured actions
Fig. 2Record and replay for repeatable workflows.

Credits

  • EngineeringRahul Kumar Singh

Next project

ApexDial AIA voice-workforce platform — bots, teams, and call records.
A dark web dashboard showing outbound call queues, bot assignments, and call transcripts