playwright-bot-bypass▌
greekr4/playwright-bot-bypass · updated Jun 7, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Bypass bot detection and CAPTCHA triggers using rebrowser-playwright with stealth techniques.
- ›Uses real GPU rendering, removes WebDriver signatures, and patches fingerprinting vectors to pass bot detection tests like bot.sannysoft.com
- ›Requires headed mode ( headless: false ) and real Chrome browser ( channel: 'chrome' ) to be effective
- ›Includes addInitScript to remove navigator.webdriver property, the most common detection method
- ›For Python, recommends undetected-chromedriver over
Playwright Bot Bypass
Bypass bot detection systems using rebrowser-playwright with stealth techniques. This approach successfully passes bot detection tests like bot.sannysoft.com and enables automation on sites with aggressive bot protection (Google, Cloudflare, etc.).
Why Standard Playwright Gets Detected
Standard Playwright/Puppeteer exposes several automation signatures:
| Detection Point | Standard Playwright | This Solution |
|---|---|---|
| WebDriver property | navigator.webdriver = true |
Removed |
| WebGL Renderer | SwiftShader (software) | Real GPU (Apple M2, etc.) |
| User Agent | Contains "HeadlessChrome" | Clean Chrome UA |
| Chrome runtime | Missing properties | Complete chrome.runtime |
Quick Start
1. Install Dependencies
npm install rebrowser-playwright
2. Basic Stealth Script
import { chromium } from 'rebrowser-playwright';
const browser = await chromium.launch({
headless: false,
channel: 'chrome' // Use real Chrome browser
});
const context = await browser.newContext();
// Remove WebDriver property
await context.addInitScript(() => {
delete Object.getPrototypeOf(navigator).webdriver;
});
const page = await context.newPage();
await page.goto('https://example.com');
Key Components
rebrowser-playwright
Drop-in replacement for playwright that patches automation detection:
- Uses real GPU instead of SwiftShader
- Removes HeadlessChrome from User Agent
- Patches various fingerprinting vectors
addInitScript for WebDriver
The navigator.webdriver property is the most common detection method:
await context.addInitScript(() => {
delete Object.getPrototypeOf(navigator).webdriver;
});
Real Chrome Browser
Always use channel: 'chrome' to launch the user's installed Chrome:
chromium.launch({
headless: false,
channel: 'chrome'
});
Complete Example
See examples/stealth-google-search.mjs for a complete working example that:
- Bypasses bot detection
- Performs Google search
- Captures results
Testing Bot Detection
Verify bypass effectiveness at https://bot.sannysoft.com:
node scripts/bot-detection-test.mjs
All items should show green (passed).
Scripts
scripts/bot-detection-test.mjs- Test bot detection statusscripts/stealth-template.mjs- Reusable stealth browser template
Examples
examples/stealth-google-search.mjs- Google search without CAPTCHAexamples/ab-test.mjs- Compare detected vs stealth side-by-sideexamples/stealth-twitter-scrape.mjs- Twitter/X profile scraping without login
Limitations
- Requires
headless: false(headed mode) - Needs real Chrome installed (
channel: 'chrome') - Some sites may still detect based on behavior patterns
- Does not bypass CAPTCHAs, only prevents triggering them
Python Support
playwright-stealth (Limited)
Python playwright-stealth cannot fully bypass bot detection.
| Environment | bot.sannysoft.com | Google Search |
|---|---|---|
| Node.js rebrowser-playwright | ✅ Pass | ✅ Works |
| Python playwright-stealth | ✅ Pass | ❌ CAPTCHA |
Why?
rebrowser-playwright: Chromium binary-level patch → uses real GPUplaywright-stealth: JavaScript-level patch only → SwiftShader exposed
undetected-chromedriver (Recommended for Python)
undetected-chromedriver fully bypasses bot detection in Python!
| Library | bot.sannysoft.com | Google Search |
|---|---|---|
| playwright-stealth | ✅ Pass | ❌ CAPTCHA |
| undetected-chromedriver | ✅ Pass | ✅ Works! |
Installation
pip install undetected-chromedriver
Usage
import undetected_chromedriver as uc
# Check your Chrome version at chrome://version
driver = uc.Chrome(version_main=133)
driver.get("https://www.google.com")
search_box = driver.find_element("name", "q")
search_box.send_keys("your search query")
search_box.submit()
Key Points
- Uses Selenium WebDriver API (not Playwright)
- Automatically patches ChromeDriver to avoid detection
- Requires specifying
version_mainmatching your Chrome version - Check Chrome version:
chrome://version
Alternative: Subprocess
For Electron/Node.js apps, call Node.js script from Python:
import subprocess
result = subprocess.run(['node', 'stealth-script.mjs', query], capture_output=True)
Troubleshooting
Still Getting Detected?
- Ensure using
rebrowser-playwright, notplaywright - Verify
channel: 'chrome'is set - Check
addInitScriptruns before navigation - Try adding delays between actions (human-like behavior)
Browser Not Opening?
# macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
# Windows
"C:\Program Files\Google\Chrome\Application\chrome.exe" --version
# Linux
google-chrome --version
WebGL Still Shows SwiftShader?
This happens with regular playwright. Confirm import is from rebrowser-playwright:
// Correct
import { chromium } from 'rebrowser-playwright';
// Wrong - will be detected
import { chromium } from 'playwright';
How to use playwright-bot-bypass on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add playwright-bot-bypass
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches playwright-bot-bypass from GitHub repository greekr4/playwright-bot-bypass and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate playwright-bot-bypass. Access the skill through slash commands (e.g., /playwright-bot-bypass) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★29 reviews- ★★★★★Ganesh Mohane· Dec 16, 2024
playwright-bot-bypass fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Shikha Mishra· Dec 12, 2024
Useful defaults in playwright-bot-bypass — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Aanya Menon· Dec 8, 2024
Registry listing for playwright-bot-bypass matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Olivia Anderson· Nov 27, 2024
Keeps context tight: playwright-bot-bypass is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Yuki Desai· Nov 27, 2024
We added playwright-bot-bypass from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Yash Thakker· Nov 3, 2024
playwright-bot-bypass has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Dhruvi Jain· Oct 22, 2024
Solid pick for teams standardizing on skills: playwright-bot-bypass is focused, and the summary matches what you get after install.
- ★★★★★Liam Huang· Oct 18, 2024
playwright-bot-bypass is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Nikhil Iyer· Sep 25, 2024
playwright-bot-bypass has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Amina Martinez· Sep 1, 2024
Solid pick for teams standardizing on skills: playwright-bot-bypass is focused, and the summary matches what you get after install.
showing 1-10 of 29