Permission State Consistency

Keep browser permission results aligned with the active profile and BrowserContext.

Prerequisites

BotBrowser 150.0.7871.46 or newer with a matching profile package.
A profile loaded before navigation through --bot-profile or Per-Context Fingerprint.

Quick Start


chromium-browser \
  --bot-profile="path/to/profile.enc" \
  --user-data-dir="$(mktemp -d)"

Permission state follows the loaded profile together with the browser’s normal site permission decisions. No separate permission consistency flag is required.

Profile Behavior

Browser permission results are visible through web APIs, page capability checks, workers, and browser UI decisions. BotBrowser keeps these paths aligned with the selected browser and platform profile family.

BotBrowser 150 improves profile-backed permission mapping for launch profiles and per-context profiles. Permission queries and browser-side checks follow the active BrowserContext.

For Per-Context Fingerprint, set the profile before creating the first page:


const client = await browser.target().createCDPSession();
const context = await browser.createBrowserContext();
 
await client.send("BotBrowser.setBrowserContextFlags", {
  browserContextId: context._contextId,
  botbrowserFlags: ["--bot-profile=path/to/profile.enc"],
});
 
const page = await context.newPage();

Permission decisions made by the site or automation framework still apply normally. The profile controls browser-family consistency; it does not grant a site access that the user or automation policy has denied.

Troubleshooting / FAQ

Problem	Solution
Permission results do not match the intended profile family	Confirm the profile package matches the BotBrowser major version and was loaded before the first page.
A per-context page inherits another context’s behavior	Apply `BotBrowser.setBrowserContextFlags` before creating the context’s first target. Do not change identity-bearing flags after the context starts.
A site remains denied after profile setup	Check browser or framework site-permission settings. Profile consistency does not override an explicit user denial.
Headless launch exits before navigation	Check terminal output for missing, invalid, expired, or version-mismatched profile guidance. Headless mode does not show visible startup windows.

Next Steps

Per-Context Fingerprint. Apply independent profiles before each context starts.
Profile Management. Select a matching profile package and understand startup states.
Navigator Properties. Keep browser identity surfaces aligned across pages and workers.

Related documentation: CLI Flags Reference | Profile Management | Headless Server Setup

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