Skip to main content

dp-cli

A powerful CLI for DrissionPage — browser automation, structured data extraction, network listening and more.

Features

  • Anti-detection by default — not based on webdriver, navigator.webdriver is false
  • Reuse your own browser — --auto-connect (Chrome/Edge 144+, no CLI flag needed) or --port
  • Hybrid snapshot — a11y tree + Vimium-style clickable detection, catches icon-only buttons and custom menu items the a11y tree misses; every element gets an [N] ref with confidence markers (⚡ medium, ? low)
  • dp scan — fast Vimium-style listing of interactive elements (viewport-only mode available)
  • Powerful locator syntax — descriptive strings stable across navigation, plus Playwright-style pw:role=button[name="Submit"] >> nth=2 chains
  • Structured data extraction — extract + query + snapshot for scraping list pages
  • Network listening — capture XHR/Fetch requests and response bodies
  • Stealth patches — dp stealth bypasses common automation detections
  • Dual mode — browser control + pure HTTP requests
  • Shadow-root / iframe — traverse directly without switching context
  • JSON output — all commands output JSON, AI-friendly

Installation

pip install dp-cli
dp --help

Agent skill(可选,推荐)

为 AI agent 安装完整使用指南(全部命令参考 + 工作流 playbook):

dp install --skills                        # 装到 agent 的 skill 目录
npx skills add mofanx/dp-cli               # 或走 skills CLI 渠道
claude plugin marketplace add mofanx/dp-cli  # 或 Claude Code 插件市场

未安装也能用——skill 只是文档层;agent 可直接读 dp --help 或 python -m dp_cli.catalog 自举。

Quick Start

# Auto-managed browser
dp open https://example.com
dp snapshot
dp click "text:Login"
dp fill "@name=username" admin
dp press Enter
dp close

# Connect to your own logged-in browser
google-chrome --remote-debugging-port=9222
dp open https://example.com --port 9222
dp snapshot

Connect to a Normally-Launched Chrome/Edge (Chrome/Edge 144+)

No --remote-debugging-port required. Chrome/Edge 144+ exposes opt-in remote debugging via chrome://inspect (Chrome) or edge://inspect/#devices (Edge):

  1. Open your Chrome or Edge as usual (no special flags)
  2. Visit chrome://inspect/#remote-debugging (Chrome) or edge://inspect/#devices (Edge)
  3. Check "Allow remote debugging for this browser instance"
  4. Run dp open --auto-connect
dp open --auto-connect                              # auto channel: sniffs Chrome stable → Edge stable
dp open --auto-connect --channel edge              # force Edge stable
dp open --auto-connect --channel beta               # Chrome beta
dp open --auto-connect --probe-dir ~/my-profile     # custom user-data-dir

How it works

Chrome/Edge 144+ in this mode exposes only a browser-level WebSocket and omits the HTTP REST API (/json, /json/version, ...) that DrissionPage / puppeteer / Playwright depend on. dp-cli transparently handles this:

  1. Reads DevToolsActivePort from the user-data-dir → real CDP port
  2. Probes the port — if /json/version is missing, identifies this as inspect mode
  3. Spawns a local bridge (python -m dp_cli.bridge) that:
    • Synthesizes the missing HTTP endpoints from CDP calls
    • Multiplexes page-level CDP traffic over a single browser-level WebSocket via Target.attachToTarget(flatten=True)
  4. Points DrissionPage at the bridge. Subsequent dp commands reuse the same bridge.

The bridge subprocess and its port are tracked in the session file; dp close stops the bridge automatically and never quits your browser (it's your browser, not dp's).

Caveats

  • Chrome/Edge always shows an "Allow remote debugging" dialog per new WebSocket client. Since bridge maintains one WebSocket and dp commands share it, you confirm at most once per dp open --auto-connect.
  • Works with whatever profile Chrome/Edge is actually using — same cookies, logins, history.
  • Classic --remote-debugging-port=9222 mode still works unchanged via dp open --port 9222.

Hybrid Snapshot (a11y + Vimium-style)

The default dp snapshot fuses two element-discovery paths:

  1. Browser a11y tree via CDP — the structural skeleton (headings, lists, form roles, explicit <a>/<button>, any role="..." element).
  2. Vimium-style clickable detection — a JS probe that flags icon-only buttons, <div onclick>, [tabindex>=0], aria-selected, cursor:pointer elements, etc. that the a11y tree misses.

Results are deduplicated by backendNodeId and rendered with confidence markers:

Marker Confidence Triggers
none high <a href>, <button>, <input>, role=button/link/..., contenteditable
⚡ medium onclick / jsaction / tabindex>=0 / aria-selected / <audio>/<video>, or cursor:pointer + heuristic (aria-label / icon child / small square / class keyword) — catches most React/Vue icon buttons
? low bare cursor:pointer / class keyword only (no other signals); hidden unless --include-low

Output includes helpful context:

  • @top-left, @top-right, @center, @bottom … — position in the 9-region viewport grid
  • (icon) — icon-only button (no visible label, has <svg> / <img> child)
  • Shadow DOM is traversed automatically (open shadow roots)

Every element gets an [N] ref usable in any command: dp click "ref:5".

dp snapshot                     # a11y + clickable (default); high + medium markers
dp snapshot -i                  # interactive mode: only interactive elements
dp snapshot -s ".main"          # limit to specific area
dp snapshot -p "data-test"      # custom locator priority
dp scan --viewport              # only elements currently in viewport
dp scan --confidence all        # include low-confidence heuristics
dp scan --confidence high       # only the sure-thing clickables

dp scan — fast clickable-only listing

When you only need "what can I click next?" without the full a11y tree:

dp scan                         # full page, high+medium
dp scan --viewport              # only elements currently in viewport
dp scan --confidence all        # include low-confidence heuristics
dp scan --confidence high       # only the sure-thing clickables

Both snapshot and scan share the same [N] ref numbering per session, so dp click "ref:N" works regardless of which one produced the snapshot.

Playwright-style locators (pw: prefix)

Need semantic, role-based targeting on a fresh page (no snapshot required)? Use the pw: prefix. Syntax mirrors Playwright, and chains with >>:

# By ARIA role (with accessible name — exact / substring / regex)
dp click 'pw:role=button[name="Submit"]'
dp click 'pw:role=button[name=/^Sign/i]'
dp click 'pw:role=link[name=More]'         # substring

# By visible text (exact / substring / regex)
dp click 'pw:text="Login"'                 # exact
dp click 'pw:text=Login'                   # substring (case-insensitive)
dp click 'pw:text=/^log/i'                 # regex

# By form affordances
dp fill  'pw:placeholder=Search…' "chatgpt"
dp fill  'pw:label="Email"' "a@b.com"
dp click 'pw:alt="Logo"'
dp click 'pw:title="Close"'
dp click 'pw:testid=submit-btn'            # data-testid / data-test-id / data-test

# Chain with >> (each step narrows the scope)
dp click 'pw:css=.sidebar >> role=listitem[name="Chat"] >> nth=2'
dp click 'pw:css=li >> has-text="Python"'
dp click 'pw:role=list >> nth=-1'          # negative index = from end

# Raw css/xpath chunks mix freely
dp click 'pw:xpath=//nav >> role=link[name=Docs]'

Matchers: role / text / label / placeholder / alt / title / testid / css / xpath / nth / has-text / visible

Value forms: bare = substring, "quoted" = exact, /pattern/flags = regex

Visibility: role / text / has-text automatically skip elements hidden via display:none, visibility:hidden, hidden attribute, or aria-hidden="true" (matches Playwright semantics).

Shadow DOM: open shadow roots are traversed automatically.

Under the hood the matcher chain is evaluated in-page as JS, the target element is tagged with a one-shot data-dp-ref attribute, and DrissionPage resolves it by that attribute — bypassing stale classes / CSS Modules / dynamic XPath.

Anti-Detection (stealth)

Bypass navigator.webdriver, HeadlessChrome UA, empty plugins, SwiftShader WebGL, chrome.runtime missing, and other common automation fingerprints.

# One-shot: connect + apply full stealth patches
dp open --port 9322 --stealth
dp goto https://bot.sannysoft.com/

# Or apply manually on an existing session (full preset by default)
dp stealth
dp stealth --preset mild                       # webdriver + UA only
dp stealth --ua "Mozilla/5.0 ..."              # custom UA
dp stealth --feature webdriver --feature webgl # fine-grained
google-chrome --headless=new --remote-debugging-port=9222 \
  --no-sandbox --disable-dev-shm-usage \
  --disable-blink-features=AutomationControlled \
  --user-data-dir=~/.config/google-chrome
# Then on local:
ssh -NL 9322:127.0.0.1:9222 vps
dp open --port 9322 --stealth

Patched features (full preset): webdriver, UA, chrome.runtime, permissions, plugins, languages, WebGL VENDOR/RENDERER, window.outerWidth/Height.

Patches are injected via Page.addScriptToEvaluateOnNewDocument — they persist across navigations and frames. Advanced fingerprints (Canvas/Audio/font list) require a real GPU or Xvfb environment.

Data Extraction (3-step workflow)

# 1. Discover CSS class names via noise-filtered content tree
dp snapshot -i -s ".main"

# 2. Verify field selectors
dp query "css:.item-title" --fields "text,loc"

# 3. Batch extract to CSV
dp extract "css:.item-card" \
  '{"title":"css:.item-title",
    "price":"css:.item-price",
    "tags":{"selector":"css:.tag","multi":true},
    "url":{"selector":"css:a","attr":"href"}}' \
  --limit 100 -o csv -f result.csv

Project Structure

dp_cli/
├── main.py              # CLI entry point (~47 lines)
├── session.py           # Browser session management + auto-connect bridge glue
├── bridge.py            # chrome://inspect mode CDP bridge (python -m dp_cli.bridge)
├── bridge_manager.py    # Bridge subprocess lifecycle + inspect-mode detection
├── stealth.py           # Anti-detection JS patches (applied via CDP)
├── snapshot/            # a11y-tree snapshot & data extraction engine
├── output.py            # JSON output helpers
└── commands/
    ├── _utils.py        # Shared decorators & helpers
    ├── browser.py       # open / goto / reload / close / list / stealth
    ├── snapshot_cmd.py  # snapshot / extract / query / find / inspect
    ├── element.py       # click / fill / select / hover / drag / check / upload / count
    ├── keyboard.py      # press / type / scroll / scroll-to / autoscroll
    ├── page.py          # screenshot / pdf / eval / wait / console / dialog
    ├── assert_cmd.py    # assert-text / assert-url / assert-visible / assert-count
    ├── tab.py           # tab-list / tab-new / tab-select / tab-close
    ├── storage.py       # cookie-* / localstorage-* / sessionstorage-*
    ├── network.py       # listen / listen-stop / http-get / http-post
    └── misc.py          # resize / maximize / state-save / state-load / config-set

Documentation

See skills/dp-cli/SKILL.md for full workflow guide and skills/dp-cli/references/commands.md for complete command reference. Exit-code contract: ERROR_CODES.md.

License

BSD-3-Clause

Metadata

Release files for dp-cli 0.8.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dp-cli 0.8.0
File Size Uploaded Provenance
dp_cli-0.8.0.tar.gz 283.4 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for dp-cli 0.8.0
File Interpreter ABI Platform
dp_cli-0.8.0-py3-none-any.whl Python 3 none any Details

Total release size: 498.5 kB

Release files / dp_cli-0.8.0.tar.gz

Download URL dp_cli-0.8.0.tar.gz
Size 283.4 kB
Tags Source
SHA-256 checksum
How to use checksums
21e263ae53bec84e07f8c16c4fb3ccb6402000e260dda63fedd79e4131caf683
BLAKE2b-256 checksum
How to use checksums
0809b9f769c6f3e93bce8d1a9b1291bdd894ea72abf78ae5da172666e07245f5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.15

Release files / dp_cli-0.8.0-py3-none-any.whl

Download URL dp_cli-0.8.0-py3-none-any.whl
Size 215.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
874001db971c5dbc449582c328683c5542fdeca2c953642efaf46f0ad27ec62a
BLAKE2b-256 checksum
How to use checksums
c8575f699b169821c58e177d780ae7fec568795e29f5c12762ca71e3f94f99de
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.15

Security for dp-cli 0.8.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page