Antidetect browser automation and RPA

Install and share automation plugins

Open Automation → Plugins to see Official plugins and your team's library. Read the plugin instructions before installing. Installation and updates require an owner, an admin or the Manage scripts permission. Official plugins come from the server; the catalog shown in your client determines which workflows are available.

Your team can also import plugins and make them visible to the whole team, only the uploader or selected members. A new official version does not automatically replace the version installed in the team library. An authorized member chooses when to update, and the client displays any minimum client version requirement.

Plugins run on your computer and can control pages in the selected profiles. A server-delivered plugin or a plugin uploaded by another member needs local approval before its first run. Changed content needs approval again. See team permissions when deciding who can access and manage the plugin.

Run profiles and handle interruptions

Choose Run, select the profiles, fill in the inputs, and set At a time and failure retry options. Each selected profile becomes a task; tasks that have not started wait in the queue. Open Runs to inspect status, progress, logs, screenshots and results for each profile.

A plugin can open a closed profile or take over one that is already running. Stopping a run stops the corresponding plugin tasks. Whether profiles close afterward depends on the plugin configuration; the close option does not close profiles that were already open before the run. Check both the task result and the browser's state.

A plugin can request human takeover for a QR login, verification step or confirmation. Complete the step and continue from the prompt. Errors and timeouts can retry according to your settings; a manual stop or Give up does not automatically retry. Flows that submit data should check whether an earlier attempt already completed before submitting again.

CSV inputs and local schedules

Choose Data table (per profile) in the run dialog when each account needs different text or files. Import a UTF-8 CSV, match rows by profile number, name or ID, and map columns to plugin inputs. The preview validates the mapping. Set Media folder when file inputs use relative paths.

Review the account assigned to each row before starting. Empty cells keep the default input value; they do not mean that the corresponding value will be cleared. Fix reported errors, then run the profiles whose inputs you have checked.

Save a task for a one-time, daily or interval schedule. Schedules stay on this computer and run only while its console is open. Sleep or a closed client can prevent a trigger. Missed runs can be skipped or run once when the console starts, according to the saved policy. Signing in on another computer does not transfer these schedules.

Connect scripts through the Local API

Open Settings → Local API and enable Turn on Local API. The default port is 54345. The service listens only on the local computer, requires an API key in the request headers, and applies your account permissions and plan limits. Scripts can manage profiles, open a browser and obtain its CDP address for Puppeteer, Playwright or Selenium.

Common paths and fields are compatible with BitBrowser's Local API. Check the key, profile IDs and every endpoint your script uses during migration. Matching the port does not establish that an entire business workflow needs no changes. Follow the Local API guide for connection steps and the BitBrowser migration guide for source profiles.

Use MCP with an AI assistant

MCP shares the Local API port and key. Once enabled, compatible assistants such as Claude Code and Codex can list profiles, open pages, read page structure, click, type, take screenshots and run plugins. Use the MCP setup guide to connect your assistant.

Plugins visible to the current team member can appear as separate MCP tools, with inputs defined by each plugin. Credential and verification-code fill tools can enter a profile's saved account information into the page without requiring you to paste a password into the conversation. You still handle steps that require human action.

The assistant operates within the signed-in account's profile visibility, plan and occupancy rules. Specify the profiles and intended task, distinguish page content from your own instructions, and review targets and inputs before submissions or bulk changes.

Seven MCP permission categories

Enable the categories your task requires in Settings → Local API → MCP. These controls apply to MCP tools. Direct Local API requests retain their own key, account and plan checks. For manual clicks and typing across similar pages, window sync provides another entry point.

• View (always on): read status and lists such as profiles, groups and plugins, excluding passwords, 2FA secrets and cookies.
• Manage profiles is on by default: create, edit, open and close profiles, manage groups and proxies, and arrange windows.
• Web interactions is on by default: navigate, read snapshots, click, type, upload, capture screenshots, execute page scripts and fill credentials.
• Automation is on by default: run plugins, stop runs and execute page scripts on profiles.
• Delete and clean up is off by default: delete profiles or groups, clear cookies and caches, and close all profiles.
• Sensitive data is off by default: access credentials and cookies, acquire proxies containing passwords, import or export backups, and use sharing.
• API passthrough is off by default: its tool can call any Local API endpoint. The other MCP category restrictions do not constrain this tool when enabled.

FAQ