Console Suppression

Control CDP console message forwarding to maintain consistent browser behavior during automation.

Prerequisites

• BotBrowser installed and running. See Installation Guide.
• A profile file (.enc for production).
• ENT Tier1 subscription (for --bot-disable-console-message).

Quick Start

Console suppression is enabled by default on ENT Tier1. No additional configuration is needed:

chromium-browser \
    --headless \
    --bot-profile="/path/to/profile.enc" \
    --proxy-server=socks5://user:pass@proxy.example.com:1080

To explicitly enable or disable it:

# Active by default on ENT Tier1; pass =false to disable for debugging
chromium-browser \
    --bot-profile="/path/to/profile.enc" \
    --bot-disable-console-message
 
# Disable for debugging (console messages will be visible in CDP)
chromium-browser \
    --bot-profile="/path/to/profile.enc" \
    --bot-disable-console-message=false

How It Works

The --bot-disable-console-message flag ensures that console-related behavior remains consistent with a non-instrumented browser session. The console API still works normally in page JavaScript, but CDP clients do not receive forwarded console messages.

On ENT Tier1 and above, this protection is enabled by default (true). You only need to set the flag explicitly if you want to disable it for debugging purposes.

Common Scenarios

Production deployment

In production, keep console suppression enabled (the default). Your automation script will not receive console.log output via CDP, but this is the correct tradeoff for consistency:

const browser = await chromium.launch({
    executablePath: BOTBROWSER_EXEC_PATH,
    headless: true,
    args: [
        `--bot-profile=${BOT_PROFILE_PATH}`,
        "--proxy-server=socks5://user:pass@proxy.example.com:1080",
    ],
});
 
const page = await browser.newPage();
// page.on("console") will not fire - this is expected behavior
await page.goto("https://example.com");

Debugging with console output

When you need to see console messages during development, disable the suppression:

const browser = await chromium.launch({
    executablePath: BOTBROWSER_EXEC_PATH,
    headless: true,
    args: [
        `--bot-profile=${BOT_PROFILE_PATH}`,
        "--bot-disable-console-message=false",
    ],
});
 
const page = await browser.newPage();
page.on("console", (msg) => console.log("PAGE:", msg.text()));
await page.goto("https://example.com");

Important: Disabling console suppression during debugging changes the browser’s CDP behavior. Results from fingerprint-sensitive pages may differ from production.

Troubleshooting / FAQ

Next Steps

• Automation Consistency Practices. Additional techniques for maintaining a consistent browser environment.
• Performance Optimization. Production tuning guide.
• CLI Flags Reference. Complete list of behavior and protection toggles.

Related documentation: Advanced Features | Playwright Guide

Legal Disclaimer & Terms of Use  • Responsible Use Guidelines . BotBrowser is for authorized fingerprint protection and privacy research only.