
mehmetnadir/cdpilot
Browser automation이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
Zero-dependency browser automation CLI. 70+ commands, 10 test assertions, smart commands (click/fill by text — no LLM needed). MCP server for AI agents with 500x fewer tokens.
개요
Zero-dependency browser automation from your terminal. One command, full control. No config files. No boilerplate. Just npx and go. AI agents and developers need browser control that : - — npx cdpilot launch starts an isolated browser session - — No Puppeteer, no Playwright, no Selenium. Pure CDP over HTTP - — Navigate, click, type, screenshot, network, console, accessibility, video understanding, progressive anti-bot resilience, and more - — Designed for Claude, GPT, Gemini, and any LLM tool-use workflow - — Your personal browser stays untouched. cdpilot runs in its own profile - — Green glow overlay, cursor visualization, click ripples, and keystroke display keep you informed during automation - — Each project gets its own browser instance and port automatically, no conflicts - — Red toast notification appears when you hover during active automation - — Everything runs locally. No data leaves your machine cdpilot picks the right browser for what you're doing.
README
원문 README의 일부입니다. 원문 보기.
cdpilot
Zero-dependency browser automation from your terminal. One command, full control.
Quick Start
npx cdpilot launch # Start browser with CDP
npx cdpilot go https://example.com
npx cdpilot shot # Take screenshot
No config files. No boilerplate. Just npx and go.
Why cdpilot?
AI agents and developers need browser control that just works:
- Zero config —
npx cdpilot launchstarts an isolated browser session - Zero dependency — No Puppeteer, no Playwright, no Selenium. Pure CDP over HTTP
- 70+ commands — Navigate, click, type, screenshot, network, console, accessibility, video understanding, progressive anti-bot resilience, and more
- AI-agent friendly — Designed for Claude, GPT, Gemini, and any LLM tool-use workflow
- Isolated sessions — Your personal browser stays untouched. cdpilot runs in its own profile
- Visual feedback — Green glow overlay, cursor visualization, click ripples, and keystroke display keep you informed during automation
- Multi-project isolation — Each project gets its own browser instance and port automatically, no conflicts
- AI control warning — Red toast notification appears when you hover during active automation
- Privacy-first — Everything runs locally. No data leaves your machine
Browser Selection (Workload-Aware Auto-Pick)
cdpilot picks the right browser for what you’re doing. auto (default) is a
two-axis policy — extension workload × platform stability:
| Your workload | Auto-pick order |
|---|---|
Has extensions registered (ext-install) |
vivaldi → brave → edge → chromium → chrome (→ Chrome for Testing, if installed) |
| No extensions (pure automation) | chrome → vivaldi → edge → chromium → brave |
Override anytime:
cdpilot browser # show current pick + reason
cdpilot browser vivaldi # pin to Vivaldi
cdpilot browser chrome-for-testing # pin to Chrome for Testing (after installing it, below)
cdpilot browser auto # restore smart default
Why the split?
- Chrome 137+ silently drops
--load-extensionfor unpacked extensions (no error, no warning) — Google removed it from branded Chrome builds (PSA).
설치
npx cdpilot mcp설정
{
"mcpServers": {
"cdpilot": {
"command": "npx",
"args": ["cdpilot", "mcp"]
}
}
}