2026 Version Updates

【October 26, 2026】Version: 9.58.18.206

Version: v9.58.18.206
Highlights: Smoother group control · Easier script setup · Clearer AI tasks · More reliable everyday use
Coverage: Improvements to the Mbbrowser client, MbAgent, interface, and browser control components from September 1 to October 26, 2026. Some capabilities were refined throughout this period.

Overview

At the start of the day, you open a dozen browser windows and arrange them. Then you switch account groups and search for the same replies you used yesterday. When it is time to run a script, a missing component gets in the way. Often, these small repeated steps take more time than the work itself.

Version 9.58.18.206 is designed to make those everyday steps easier.

We have improved the Mbbrowser client, the MbAgent AI workspace, and the interface and browser-control components behind them. Group control is more organized, script setup comes with clearer guidance, AI task progress is easier to follow, and window, sign-in, and older-core behavior has been refined.

Start with the task that matters to you: arrange a group of browser windows, save reusable text, or ask MbAgent to help with a small, specific task. Spend more time on your work and less time repeating setup.

Find the changes that matter to you

How you use Mbbrowser	Improvements to explore
Manage several account environments at once	Window layout, group history, environment order, and reusable text groups
Run automation scripts regularly	Check required components before running, install missing ones when needed, and view progress
Use MbAgent as a work assistant	Clearer task states, selectable options, account usage, and browser-automation setup
Use high-resolution or multiple displays, or older browser cores	Refined images, dialog placement, window edges, and group control for older cores

1. 🧭 Group control: Get organized before you get to work

📌 In a nutshell: Spend less time arranging multiple browser windows and get to the right environment sooner.

Windows wait until they are ready, then move into place

When you start several environments, Mbbrowser arranges them using the main environment, the order you chose, and the usable area of your displays. Windows are placed after the browsers are ready, reducing the jumble and movement that can happen during startup.

Position calculations have also been refined for multiple displays and different Windows scaling settings. This helps reduce windows landing off-screen or displaying awkwardly at the edges.

What you will notice:

The main environment and the others follow a clearer order, so it is easier to find a window after a batch start.
Drag environments into the order that suits your work, and keep that order.
Group-control status updates more promptly when you resume, run, or stop a group.

Main improvements: October 11–25, 2026.

Find group history and settings more easily

If you switch between projects or account groups, group history can help you find a previous setup. Search and view past groups, then return to the current one. History and search preferences are saved per signed-in account to reduce mix-ups when accounts change.

Group settings, such as window arrangement, are kept in a dedicated configuration window. Simply opening and closing the window without making changes will not create a new history entry.

Main improvements: October 15–20, 2026.

2. 📝 Reusable text groups: Prepare it once and find it again

📌 In a nutshell: Save frequently used text in separate groups so it is easier to find when you need it.

Customer replies, product descriptions, and project-specific text can end up scattered across notes and chat windows. Group-control settings now let you organize reusable text into tabs, with support for multiple lines.

What has changed?

Keep different sets separate. Add or remove text groups using tabs. Mbbrowser asks before deleting a group that contains edited text.
Prepare text before opening an environment. Save a draft while group control is stopped, then use it when the environment is ready. Editing a draft does not type into a web page.
Find your text again after switching. Drafts are restored for the current account and group when you switch tabs or reopen the panel, reducing the chance that old content or an empty value replaces your work.

For example: Create one group for product descriptions and another for customer replies. Prepare them in the morning and select the right text when you are ready to work.

Main improvements: October 19–21, 2026.

3. 🧰 Script setup: See what is missing before you install it

📌 In a nutshell: Check a script's requirements first, so a missing component does not stop you without an explanation.

For a first-time script user, names such as Python, Java, Node.js, and Playwright can be confusing. Think of them as different tools that some scripts need in order to run.

The automation script manager can check the components needed for a script. If something is missing, it explains the next step, lets you confirm before downloading, and shows installation progress and results.

From “it will not run” to “I know what to do next”

Check first. Mbbrowser checks whether the required components are actually usable, rather than relying only on the presence of a folder.
Confirm setup. If a component is missing, follow the prompt and view download progress.
Run when ready. Mbbrowser checks again after installation. If you cancel or setup fails, the script will not continue to run.

Checks for Python and Java, as well as compatibility fixes for some Playwright folders and launch methods, have also been improved.

A simple way to get started

Open the automation script manager, choose the script you want to use, and follow the component prompts when you run or debug it. Once setup is complete, try the script with a test environment first.

Main improvements: October 21–25, 2026.

4. 🤖 MbAgent: Follow what the AI is doing

📌 In a nutshell: See more than the final reply: follow the work in progress and know when MbAgent needs your input.

Clear task states and options you can select

MbAgent groups activity from tools such as files, commands, and the browser, and shows whether work is running, complete, failed, or waiting for your approval. When the AI offers fixed choices, you can select one directly. On narrow windows, the choices rearrange to avoid crowding.

Web-task results are handled more carefully, too. The app distinguishes between an automation process ending and an actual result being returned, reducing the chance that an unfinished task appears successful.

That means you can see when work is underway, respond when needed, and judge the result more easily.

Main improvements: September 1–October 15, 2026.

Prepare browser automation when you need it

MbAgent can check whether its browser-automation component is ready, download and install it when needed, and show setup progress. Before starting a web task, it checks that the Mbbrowser environment and browser connection are ready.

Longer tasks also have improved protection against repeated actions, timeouts, and failures. Available features still depend on your installed version, Windows version, browser core, and account permissions.

Main improvements: September 13–October 22, 2026.

Find templates, project details, and account usage

Not sure where to start? Try an official task template for network checks, client checks, backups, or common web workflows.
Working on a project? Start an AI task from the project page using the selected workspace and project materials, or open the current workspace folder directly.
Want to check your usage? The sidebar can show your total, used, and remaining account allowance. Sign-in status also refreshes sooner after you log in or out.
Having a longer conversation? Updates to multi-turn model support and official information search help reduce repeated searches and some mid-conversation errors.

Start with one clear task

Try a task template such as checking the Mbbrowser client version or reviewing your network connection. Follow the steps and result before moving on to more complex tasks. AI features and models depend on the permissions available to your account.

Main improvements: September 3–October 20, 2026.

5. 🪟 Windows and interface: A little more polish in everyday use

📌 In a nutshell: Less flicker and fewer misplaced windows; clearer, smoother everyday operation.

Updates to the client and its interface foundation appear directly in Mbbrowser. There is no separate interface tool to install.

Everyday situation	What has improved
High-resolution displays or Windows scaling	The interface chooses image resources at a more suitable scale
Resizing a window or dragging a list item	Redraw and drag handling are refined to reduce trails and incomplete updates
Starting with the app minimized to the tray	Less chance of the main window flashing on screen before hiding
Confirming exit while the main window is minimized	The confirmation dialog is placed using the active display
Snapping MbAgent next to Mbbrowser	Clearer spacing and less unwanted movement when dragging the main window
Opening the client or MbAgent	Key interface state is prepared before the window appears, reducing blank or unfinished screens

Sign-in input behavior has also been refined to reduce keyboard-input interruptions. Common interface resources for the main window, settings, proxies, scripts, and group control have been updated.

Main improvements: September 30–October 25, 2026.

6. 🔄 Support for new and older browser cores

📌 In a nutshell: Improvements continue for older browser environments as well as newer ones.

Group control continues to improve on older cores

Group-control components for Chrome 86, 87, and 105 have been updated. Work focused on everyday operations such as managing windows and tabs, scrolling, typing, selecting text, and synchronizing clipboard content. Per-environment results and recovery after an error are clearer as well.

You do not need to switch an existing environment to a different core to benefit from these improvements. Choose an installer that matches your current environment, then check that the specific feature you need is supported.

Main improvements: October 23–25, 2026.

Proxy, startup, and shutdown behavior is more reliable

Proxy checks better reflect the actual connection. Mbbrowser favors the real external address when checking availability, reducing false failures caused by a location lookup problem.
A Chrome 105 proxy issue has been corrected. Startup now passes proxy settings more reliably, including when a password contains special characters.
Readiness is checked before group control starts. If the browser or its control component is not ready, Mbbrowser stops and reports the problem more accurately.
Browser processes are cleaned up more reliably. This reduces cases where the environment closes but related background processes remain.

Some environment setup now runs in the background, so creating an environment is less likely to hold up the interface. Closing an import preview also stops further reading, and previewing a script package does not rewrite the saved script information.

Main improvements: September 1–October 25, 2026.

7. ✨ Start with the step that slows you down most

If you manage several environments every day, try the updated group layout and reusable text groups. If you run scripts, check the required components once. If you want to try AI assistance, start with one MbAgent task template.

The value is in the everyday details: fewer searches, fewer setup surprises, and less time arranging windows.

You do not have to learn everything at once. Make one frequently used feature part of your routine, then explore more when you are ready.

8. 📥 Download version 9.58.18.206

When upgrading an existing environment, choose a browser core that matches the one it already uses. For a fresh installation on Windows 10/11 with no older environments to preserve, you can start by considering Core 140. On Windows 7, choose one of the compatible older-core installers.

Browser core	Supported Windows versions	Download
Chrome 140	Windows 10 / 11	Download 9.58.18.206 · Core 140
Chrome 129	Windows 10 / 11	Download 9.58.18.206 · Core 129
Chrome 105	Windows 7 / 10 / 11	Download 9.58.18.206 · Core 105
Chrome 87	Windows 7 / 10 / 11	Download 9.58.18.206 · Core 87
Chrome 86	Windows 7 / 10 / 11	Download 9.58.18.206 · Core 86

Read before upgrading

1. Know the difference between the software version and browser core

The software version is 9.58.18.206. The Core 140 / 129 / 105 / 87 / 86 in each installer refers to the browser core. A software update does not automatically mean that an existing environment should switch to a different core.

In the address bar of your current environment, open chrome://version and note the full browser version before choosing an installer. If an environment uses Core 105, start with the Core 105 installer; if it uses Core 140, start with Core 140.

Important: keep existing business environments on a matching core

Switching an environment to a different core may affect saved sign-in details or website compatibility. Matching only the major number, such as “140,” may not be enough: check the full browser version. If you are unsure which installer matches your environment, ask official support before installing. Do not overwrite an existing business environment with a different core.

2. Back up first, then test with a small number of environments

Back up important environments and data before upgrading, and keep the existing data directory. After installation, open or import a small number of test environments. Check website sign-in, proxy access, extensions, and your regular scripts before gradually moving more business environments over.

3. Choose an installer that fits your Windows version and needs

Core 140 and 129 installers are for Windows 10/11. Windows 7 users should choose Core 105, 87, or 86. MbAgent and browser automation also depend on your Windows version, browser core, and account permissions. The availability of group control on older cores does not mean that every core has the same AI features; follow the prompts shown in your installed version.

4. Follow the prompts the first time you run a script or AI task

If a script tool or browser-automation component is missing, review the prompt and confirm its installation before continuing. When trying a new task for the first time, check the result in a test environment before using it for business work.

📢 Not sure which installer to choose, or having trouble after upgrading? Contact Mbbrowser support and share your software version, full browser version, and what happened so the team can help more quickly.

【September 21, 2026】Version: 9.18.58.198

Version: v9.18.58.198
Kernel Version: 140.0.7339.248 Build 20260921
Update Level: Major / Strategic Update Codename: "ApexCortex"

Version Overview

If v8's ControlMatrix made "managing hundreds of environments at once" a standard Mbbrowser capability, this ApexCortex release answers a more fundamental question: when your workflow is more than just "open a browser and click around," can Mbbrowser help you truly "think + work"?

Over the past three years, Mbbrowser has been solving three things: account security, fingerprint stability, and large-scale environment management. From v7.10 (IphoneCloudFlare), v7.12 (MBBridge + MBLink), to v8.12 (ControlMatrix), every major release reshaped some underlying layer of multi-account operations. Today, v9.18.58.198 marks the first time Mbbrowser officially steps beyond being a browser tool into becoming an AI collaborative workspace.

mbAgent debuts.

It is a local AI agent natively co-existing with Mbbrowser, specialized in "web pages + Mbbrowser + multi-account scenarios." It is neither a simple ChatGPT wrapper nor yet another browser automation engine. Instead, it takes the fingerprint, proxy, environment, CDP, Control V2 protocol, and dual-controller capabilities Mbbrowser has built over the years and hands them in full to AI — AI can now directly command Mbbrowser to open any environment, log into any account, and execute any web task, all while respecting Mbbrowser's security boundaries, audit logs, and token quota management.

Alongside mbAgent, an officially certified web automation engine — browser-auto (Mbbrowser Web Automation Engine) — ships built-in. It is a hardened independent EXE subprocess adapted by the Mbbrowser team on top of the mature upstream browser-use engine, purpose-built for complex cross-border e-commerce pages (registration, multi-step forms, dynamic captchas, login redirects, submission sending).

Around the debut of mbAgent, the mbbrowser client, ApiServer controller, Cookie governance, and official AI model channels have all completed a strategic-level upgrade:

mbbrowser (Mbbrowser Client) — The Control V2 server side has been fully rewritten to dual controllers, officially carrying mbAgent connections; Cookie expiry reminder email service has been added; multi-window interaction details have been polished throughout.
ApiServer — All 144 historical HTTP endpoints have been migrated to Control V2, sharing the same capability spec with mbAgent; once mbAgent is started, both controllers can be used simultaneously.
Multi-LLM Official Channels — Three categories of officially certified models (DeepSeek / Claude / GPT) automatically unlock based on your Mbbrowser membership tier, billed and audited through Mbbrowser's own NEWAPI relay station.

We recommend that all users engaged in cross-border e-commerce, multi-account matrices, ad placement, e-commerce store operations, and social media traffic operations upgrade immediately after reading this announcement — v9.18.58.198 is the starting point of Mbbrowser's transition from a "tool product" to an "AI workspace."

1. 🧭 Major Debut: mbAgent — Mbbrowser's Native AI Agent

📌 In one sentence: From today, the Mbbrowser client ships with a local AI assistant for cross-border e-commerce scenarios. You can tell it directly in plain language "fetch all today's new messages from pcmax.jp in this environment," and it will complete every step automatically.

What problem does this feature solve?

Anyone in cross-border business knows that "whether AI can truly help us work" has always been an awkward question:

Generic ChatGPT / Claude web versions: Accounts live in the cloud, can't reach your Mbbrowser environments, and certainly can't use them to operate fingerprint-protected real business sites like pcmax, TikTok, or Shopee.
So-called "AI browsers" on the market: Run in parallel with Mbbrowser and conflict with Mbbrowser's fingerprint, proxy, Cookie, and pipeline; they can't manage your Mbbrowser profiles.
Writing your own scripts: Login, captcha, two-factor, page changes... each item can take a full day to debug.

mbAgent is the first AI agent natively running inside the Mbbrowser client. Its arrival is not meant to replace Mbbrowser's existing browser experience, but to upgrade it one layer: turning the Mbbrowser browser into an intelligent execution unit that AI can command, supervise, and summarize.

A standard mbAgent workflow is: you give a goal → mbAgent picks an environment → attaches to Mbbrowser Chromium → executes the complex page task → returns the process and result to you.

mbAgent LLM Capabilities Overview

What can mbAgent do for you?

mbAgent ships with 130+ preset task templates (see Section 4 for details), covering the full cross-border e-commerce scenario set. At the same time, you can describe new tasks freely in natural language; mbAgent will automatically decompose, plan, and execute them directly through your Mbbrowser environments.

Typical scenarios:

"Check whether all 200 store accounts today have any abnormal login regions" — mbAgent traverses environments, checks proxy exit IPs, compares historical fingerprints, and generates a report.
"Log into pcmax.jp in the current environment and organize all unread messages into Excel" — mbAgent attaches to the environment you opened, and completes the flow step by step under your Mbbrowser identity.
"The Product Description format on this Amazon seller page is messy. Rewrite all products using a unified template and save locally" — mbAgent opens the page, extracts structure, rewrites per your template, writes the file.
"Before 9 PM tonight, automatically open 50 environments, visit a website in sequence, each staying for 30 seconds" — mbAgent starts 50 environments through Mbbrowser Control V2 and executes them in order.

How does it do all this? — Its relationship with Mbbrowser

This is the most fundamental difference between mbAgent and every "AI browser" / "AI assistant" on the market.

User
  ↓ Natural language task description
mbAgent main agent (Rust local process)
  ↓ Calls "published" operations in the Mbbrowser spec
Mbbrowser (mbbrowser.exe)
  ↓ Control V2 protocol / environments started and managed
Mbbrowser Chromium 140
  ↓ Candidate attach + automation lease
Mbbrowser CDP (WebSocket)
  ↑ Page state, proxy exit, Cookie values, cross-origin frames
browser-auto (Mbbrowser Web Automation Engine, independent EXE)
  ↑ Model loop: observe → decide → act → verify → recover
LLM (DeepSeek / Claude / GPT, per membership channel)

mbAgent does not invoke LLM in the cloud to operate an independent Chrome. Instead, it:

Discovers and connects to the Mbbrowser client already logged in on your machine (validated via triple-check: Control V2 + discovery token + PID creation time);
Selects available environments per Mbbrowser profiles, verifying each environment's fingerprint / proxy / Cookie / previous state;
Attaches to the real CDP WebSocket of Mbbrowser Chromium (does not create profiles, does not modify fingerprints, does not switch proxies);
Calls "published" operations in the Mbbrowser official spec (144 historical HTTP endpoints + 4 ApiServer local management endpoints, all over Control V2 persistent TCP);
Uses Mbbrowser's AutomationLease to seamlessly hand off to human takeover — you can take over the environment mbAgent is operating at any time; it will automatically yield control.

This means: mbAgent never bypasses any Mbbrowser security mechanism, and never touches your fingerprint / Cookie / proxy. It simply lends Mbbrowser's capabilities to AI.

2. 🚀 Brand-New Independent Engine: browser-auto (Mbbrowser Web Automation Engine)

📌 In one sentence: browser-auto is the "engine" behind mbAgent — an independent EXE subprocess purpose-built for complex web tasks.

Why does it need to be an independent engine?

The mbAgent main agent (Rust) excels at scheduling, spec validation, capability discovery, and audit, but it is not good at "looking at a web page and making decisions." To make AI operate real websites like a human, you need a complete, mature, observable web agent loop:

observe (DOM / screenshot / control tree)
  → model_decide (LLM decides the next action)
  → action (click / input / submit / send)
  → verify (whether page change matches expectation)
  → recover (rollback and retry if not)

After deep evaluation, the Mbbrowser team packages the mature upstream browser-use 0.13.8 as the Mbbrowser-branded browser-auto. While preserving the full upstream capability set, we applied the following hard hardenings:

Standalone/onedir EXE (Nuitka), with no dependency on Python, uv, or pip — works out-of-the-box on the target machine;
Communicates with mbAgent only via anonymous stdio NDJSON, with no TCP / HTTP ports listening, no Windows service registered, minimal exposure surface;
Can only attach to Chromium started by Mbbrowser Control V2 — prohibited from launching Chrome on its own, prohibited from creating profiles, prohibited from modifying proxies, prohibited from overwriting fingerprints;
API Keys are passed only in memory — never written to .env, never written to the command line, never embedded in EXE resources;
On first launch, disables anonymous telemetry, default extensions, PostHog, and all third-party leakage points;
Candidate attach + automation lease — browser-auto, mbAgent native page tools, and human takeover share the same "who is operating this page right now" lease, preventing concurrent write conflicts.

All 24 upstream default actions in browser-auto are fully preserved (click, input, send_keys, submit, send, purchase…), with no modification, no trimming, and no extra gating.

Relationship with mbAgent native page tools (candidate pages)

mbAgent supports both page capability sets, complementing each other:

Engine	Suitable Scenario	Dispatch
browser-auto (default)	Complex, multi-step, forms, dynamic pages, captchas, registration, login redirects	One task-level grant → continuous actions internally
mbAgent candidate pages (fallback)	Deterministic read-only diagnostics, single-step actions, Windows 7 / legacy kernel compatibility	Per-action validation

Mbbrowser does not delete or replace any existing capabilities. browser-auto is an added "advanced option," and candidate pages continue to serve as a safety fallback.

The difference you will feel

Before: "Help me log into the account" → make the user write 50 lines of Puppeteer / Selenium script → debug for twenty minutes.
Now: "Help me log into the account" → mbAgent + browser-auto handle it in one sentence; the process log is traceable locally in Mbbrowser.

3. 🌐 Brand-New Official AI Model Channels: DeepSeek + Claude + GPT

📌 In one sentence: The LLM invoked by mbAgent is provided through Mbbrowser's official channels, automatically unlocked based on your Mbbrowser membership tier, billed and audited through Mbbrowser's self-built NEWAPI relay station.

What problem does it solve?

The three biggest fears of running AI business: API keys flying around, token usage out of control, black-box models. mbAgent resolves all of this through Mbbrowser's own account system:

Log in on the Mbbrowser client — the system automatically creates/updates a shadow user in NEWAPI, generates an account-specific Token, and binds the subscription.
In the WEB console, check the model whitelist available for your membership tier (mb_fast / mb_claude / mb_premium).
When mbAgent starts, it pulls the whitelist and, per the official Mbbrowser profile, decides whether to go through /v1/chat/completions or /v1/responses — decided by what the profile actually declares, not guessed by name.
Every model call returns real token usage back to the Mbbrowser client logs and the official billing system.

Chat and Responses both supported

mbAgent's built-in browser automation assistant supports both Chat Completions and Responses protocols. The Mbbrowser official profile declares api_mode=chat_completions or api_mode=responses; mbAgent routes based on the actual declaration:

Protocol	Use Case
Chat Completions	General conversation, legacy compatibility, stable and reliable
Responses	Structured output, reasoning_effort, vision input (future)

You don't need to understand the difference between these two protocols — Mbbrowser has already made the choice for you. You only need to select your model in the WEB console.

Model categories and membership tiers

Category	Model Examples	Applicable Membership
mb_fast	DeepSeek series	All users (including free tier)
mb_claude	Claude Sonnet	Personal / Team members
mb_premium	GPT series	Personal / Team members

💡 NEWAPI Tokens use short leases (15 minutes). When an account is deactivated, downgraded, or a model is removed, the token automatically expires. Old keys can never remain valid permanently.

Audit and redaction

All model responses entering mbAgent undergo mandatory redaction:

API Keys never appear in LLM context, UI, logs, or IPC;
Large-volume data such as HTML / DOM / screenshots / network bodies are kept only as task-scoped ephemeral artifacts, and the LLM reads summaries and chunked indices on demand;
Token usage is itemized per Prompt / Completion / Cache, bound to model + task + time.

📌 In one sentence: An icon called "Start Menu" appears at the top of the AI chat interface in the Mbbrowser client; clicking it reveals 130+ preset AI tasks for cross-border scenarios.

What is this for?

Many users ask on their first time using mbAgent: "I don't know what to ask AI to do." The Start Menu is the task template library maintained by Mbbrowser officially, covering 8 major cross-border e-commerce scenarios:

📁 Mbbrowser Client O&M and Detection (10)
   ├─ Client startup crash and abnormal exit root-cause analysis
   ├─ Client process subprocess and residual process detection
   ├─ Client version, browser kernel version and update status detection
   └─ ……

📁 Operating System Health Detection (10)
   ├─ CPU, memory, disk, and temp directory health detection
   ├─ System time, timezone, language, and regional settings detection
   ├─ Firewall, system proxy, and security policy detection
   └─ ……

📁 AI Memory Data and Backup Security Check (9)
   ├─ AI local memory expired, duplicated, and contradictory info detection
   ├─ Token, Cookie, password, and key exposure risk detection
   ├─ Session records, config files, and browser environment backup detection
   └─ ……

📁 Browser Fingerprint and Environment Diagnostics (9)
   ├─ Canvas / WebGL / audio / font and media device exposure detection
   ├─ WebRTC, DNS, IPv4 and IPv6 leak detection
   ├─ Timezone, language, geolocation, and proxy exit coordination detection
   └─ ……

📁 Proxy and Network Diagnostics (10)
   ├─ DNS resolution path and DNS leak detection
   ├─ Proxy IP attribution, ASN, and residential / datacenter trait breakdown
   ├─ Proxy latency, packet loss, stability, and bandwidth detection
   └─ ……

📁 Account and Environment Isolation Patrol (9)
   ├─ Cookie, local storage, cache, and IndexedDB isolation detection
   ├─ IP, proxy, and device parameter cross-account reuse risk detection
   ├─ Login records, session state, and duplicate-login reason breakdown
   └─ ……

📁 Business Operations and Web Workflow Assistance (8)
   ├─ Product content publish and edit flow orchestration
   ├─ Web form field pre-submission validation
   ├─ Customer service message handling and pre-send review
   └─ ……

📁 Software Version and Upgrade Compatibility Check (9)
   ├─ CDP and Control channel version handshake compatibility detection
   ├─ Upgrade package source signature and hash verification
   └─ ……

Highlights

Officially maintained: Task templates and prompts are continually updated by the Mbbrowser team based on real business; new "business flows" require no code from users;
User-level customization: You can also write your own "experience" into the template library and share it across accounts;
Permission isolation: Official and personal templates are strictly physically isolated — AI will not "pollute" your local business preferences with official policy;
Can be turned off: If you don't want the menu, you can disable it directly in settings with zero impact on formal workflows;
Recent tasks: The right side displays your 5 most recent tasks in reverse chronological order; click again to rerun.

5. 🤖 ApiServer and mbAgent Dual-Controller Coexistence

📌 In one sentence: The same Mbbrowser instance can be connected by ApiServer and mbAgent at the same time — no interference, no contention.

What problem does this mechanism solve?

Cross-border teams have long faced a contradiction: automation scripts (Puppeteer / Selenium / custom APIs) and AI operations often cannot run at the same time — when one connects, the other is either rejected or sees garbled data.

After this update:

The same Mbbrowser instance accepts up to 1 ApiServer + 1 mbAgent connection;
The two connections use independent bounded queues (MBAGENT 75% / APISERVER 75%), with FIFO fair rotation — one role cannot starve the other;
All write operations support idempotency keys — switching mbAgent and ApiServer retrying the same task only executes it once;
Mbbrowser Control V2 provides SNAPSHOT frames — when either side switches, disconnects, or pauses, the other can obtain a consistent environment snapshot and continue execution;
Mbbrowser runtime identity (PID / run_id / endpoint_generation / real /json/version) is strictly verified — impersonation cannot take over.

Actual usage

You can arrange it like this:

Morning: mbAgent runs content collection across 50 environments (one task-level grant, browser-auto runs long);
Afternoon: Your Python scripts take over these 50 environments through ApiServer for batch publishing;
The two tools do not fail because of each other's presence.

The mbAgent capability ledger

The Mbbrowser capabilities mbAgent can invoke are generated from a single unified spec:

        mbAgent Profile
            ↓
    MbbrowserDescribe (fetch the manifest)
            ↓
    MbbrowserExecute (invoke per operation)
            ↓
    Control V2 → mbbrowser → real business

170 semantic operations
150 routes (144 of which are ApiServer-compatible; 6 are ApiServer local management)
19 canonical workflows (auth, list environments, start, Cookie, plugins, scripts, proxy, UA, advanced settings, system mode, force-kill, cache cleanup, …)
Every operation carries strict Request / Response / Error schemas, risk level, write impact, idempotency key, TTL, and revocation semantics

This spec is simultaneously the single source of truth for the Apidog / Postman collection, Python SDK, TypeScript SDK, and mbAgent tool registry. Whenever the spec updates, every client refreshes in sync — no "AI knows one way, scripts know another" fragmentation.

📌 In one sentence: Cookies are the "login credentials" of an account — Mbbrowser can now actively monitor them and email you proactively before expiry, instead of waiting for the account to drop offline.

What is this for?

Anyone running multi-account matrices knows: sudden account dropouts = sudden business interruption = customer complaints / losses. One of the most common causes of dropout is Cookie expiry:

Temporary Cookies (Session) only cover the current session — refresh, and they're gone;
Long-term Cookies last days to weeks; timezone changes, User-Agent changes, and IP changes can all cause the peer server to actively invalidate them;
You operate 100 accounts — it is impossible to track Cookie expiry times by hand.

How does Mbbrowser help?

New feature: Cookie expiry reminder email built into the Mbbrowser client:

Mbbrowser local heartbeat
  ↓ Polls every 30 minutes
For each reminder-enabled Cookie:
  - Remaining validity < threshold (default 24h)
  - Time since last reminder > 600s
  ↓ Pass
Construct SMTP email:
  - Recipient = email bound to current Mbbrowser account
  - Subject = "[Mbbrowser] Cookie for environment <name> expires at <time>"
  - Body = "Please log into the business website again in this environment to have the server re-issue the login state"
  ↓ Send
Async SMTP delivery
  ↓
Mbbrowser local log + Mbbrowser log manager

Key details

Whitelist and blacklist: 13 default renewable Chromium caches can be cleaned; business data such as Cookie / History / Preferences will never be accidentally cleared;
Stop reminding after fix: Once you complete the actual login through the reminder email and the Cookie is renewed, Mbbrowser automatically stops subsequent reminders;
Multi-environment batch reminders: Reminders are sent in a fixed time slot to avoid 100 emails at once when 100 Cookies nearly expire simultaneously;
SMTP test send: Click "Test SMTP Configuration" in the settings panel to immediately verify the email chain works;
Retry and dedup: SMTP failures retry with 30s/2min backoff to avoid repeated interruptions in a short time;
Local-first: All reminder records are first written to Mbbrowser local logs; SMTP failures will not be misreported by Mbbrowser as Cookie issues;
Third-party email supported: QQ Enterprise Mail, NetEase Enterprise Mail, Alibaba Cloud Mail, SendGrid, Mailgun, and self-hosted SMTP all work.

Important notice

⚠️ For websites using JWT, server-side sessions, or complex risk control, merely modifying the local Cookie time is not the same as a real renewal. The correct approach is still to log into the business website again in the corresponding environment so the server side issues a fresh valid login state. Mbbrowser's reminder email also states this explicitly.

7. 🔁 mbbrowser Client: Control V2 Dual-Controller Protocol Fully Enabled

📌 In one sentence: Mbbrowser's underlying control protocol has been completely rewritten — designed specifically to support the mbAgent + ApiServer dual-controller setup, with significantly higher security and throughput.

What is Control V2?

Mbbrowser previously used a custom TCP + Protobuf protocol for mbBrowser ↔ ApiServer communication (144 HTTP endpoints + 30 legacy commands). That protocol is no longer sufficient for new scenarios like mbAgent, which require long-lived sessions, bidirectional streaming events, and strict identity verification.

Control V2 is the next-generation underlying control protocol Mbbrowser rewrote for mbAgent:

Feature	Legacy Protocol	Control V2
Connection model	Short-lived, HTTP Bearer	Persistent TCP, MBV2 frame header + CRC32 + sequence number
Role	ApiServer only	MBAGENT + APISERVER dual slots, fair rotation
Identity verification	HTTP Token (deprecated)	64-byte instance_id + discovery token + PID + process creation time quadruple
Write idempotency	Not guaranteed	Persistent idempotency store + Windows DPAPI + 24h/4096 bounded + failure rollback
Cancellation	Complex	Independent cancel_id + CancelAck + filter by connection_generation
Event stream	Single-slot serial line	1024 / 4MiB / 1h triple backpressure + EVENT_GAP snapshot recovery
Write concurrency	Global FIFO	75% per role cap + global 256 cap + wait table + deadline

Details of mbAgent integration

Mbbrowser service discovery: After mbAgent starts, it reads two files under LOCALAPPDATA\MBBrowser\browser\control, protected by the current user's ACL:

discovery — contains the handshake token (readable only by mbAgent and ApiServer)
instance — does not contain a token; describes instance_id / PID / creation_time / generation

After verifying the discovery token + PID + creation time four factors, mbAgent establishes a persistent TCP. Mbbrowser startup mandates INADDR_LOOPBACK (127.0.0.1); remote connections are not supported.

Sensitive fields such as API Key, Cookie, Authorization, CK, sessionId, objectId:

Never enter model parameters, command lines, regular logs, UI, or IPC;
Mbbrowser's ChromeParam handles are replaced with random candidate_* IDs in IPC;
Once the Mbbrowser process starts, secrets like CK / CDP ports are immediately placed in Zeroizing memory; they never enter generic fields during IPC serialization.

Start and stop

The same Mbbrowser instance only accepts 1 MBAGENT + 1 APISERVER, each with 1 connection;
A second connection of the same role is rejected outright (returns SLOT_OCCUPIED);
Slot is automatically reclaimed on heartbeat timeout or crash; a new connection can reattach within 30s;
After mbAgent or ApiServer disconnects, Mbbrowser Chromium is not closed and the main process is not terminated — the mbbrowser lifecycle is fully decoupled from the controller.

Compatibility

All 144 historical ApiServer HTTP endpoints are fully preserved; legacy business code connects to Control V2 with zero changes;
ApiServer is gated by MBAPISERVER_CONTROL_V2=required/auto/off for gradual rollout;
mbAgent is gated by MBAGENT_DIRECT_CONTROL=on/auto/off;
All new features go through unbiased-rejection sampling in the rollout bucket + 1M-sample validation.

8. 🛡 Security / Efficiency Improvements You Will Feel Immediately

This section covers changes you can perceive directly as a user, not internal API details.

✅ UI improvements you will see

Main interface: Group menus, single-environment more-actions menu, Cookie menu, proxy menu, and environment package import/export menus are all wired to the multilingual mechanism; new buttons are auto-localized (zh-CN / en / zh-TW / ru / ja / vi / id / tr / th / es / pt / uk);
List controls: Selected background, hover background, and selected indicators are uniformly refreshed, fixing the legacy issue of "selected background being covered";
Scroll behavior: All data lists support smooth scrolling + inertial wheel + improved scrollbar thumb;
Icons: codicon.ttf fully covers menu buttons, toolbar, and status indicators — DEBUG verified, RELEASE synced;
Window close / state switch: Refresh is more stable; errors no longer "freeze the list".

✅ Features you will feel directly

Cookie expiry reminder email: detailed in the previous section;
Multi-LLM model channels: detailed in the previous section;
Start Menu: detailed in the previous section;
browser-auto engine: detailed in the previous section.

✅ Background operations improvements

More stable multi-instance upgrade: mbAgent upgrade → full Control V2 snapshot freeze → environment fingerprint not reset → business not interrupted;
More stable Proxy batch assignment: All proxy operations go through atomic transactions + persistent baseline snapshot + same-value replay without rewrite;
Safer command invocation: Batch start requests have independent request_id; late packets do not wake up the next start; account / environment start results do not cross over;
Smaller token footprint: The twelfth round of performance optimization thoroughly improves slow LLM responses and wasted tokens.

9. 📚 Companion Action: Mbbrowser Official Documentation Synced

This release also pushes Mbbrowser's official documentation system into the AI era.

Client embedded documentation

The Mbbrowser client embeds 130+ AI-assisted task manuals plus core concept / basic knowledge Q&A, classified into:

Mbbrowser Client O&M and Detection (10)
Operating System Health Detection (10)
AI Memory Data and Backup Security Check (9)
Browser Fingerprint and Environment Diagnostics (9)
Proxy and Network Diagnostics (10)
Account and Environment Isolation Patrol (9)
Business Operations and Web Workflow Assistance (8)
Software Version and Upgrade Compatibility Check (9)
mbAgent Basic Usage (10)
Proxy and Network Basics (13)
Mbbrowser Safe Usage (10)
Frequently Asked Questions Basics (10)
Core Concepts (10)
Account Isolation Basics (10)
Fingerprint Parameter Basics (10)

All 130+ documents are automatically loaded in the background by mbAgent after the first upgrade, and grouped by topic into the "Start Menu" and the AI recommended-reply material library.

Help documentation site

The help.mbbrowser.com help center is synced:

Update log (where this announcement lives)
mbAgent user guide: a complete walkthrough from install to the first task
mbbrowser feature tutorials: including Cookie expiry reminder email in this release
API documentation: 30+ ApiServer endpoints (HTTP + Control V2 dual protocols)

10. ⚙ Read Before Upgrading

Same-kernel version is mandatory

You must upgrade with the same kernel version. For example, if your previous kernel version is 140.0.7339.248, the installer you upgrade to must also be 140.0.7339.248; otherwise, a kernel mismatch may create account credential loss risk.

Built-in browser kernel (Chromium)

140 kernel: Windows 10 / 11 (recommended)
129 kernel: Windows 10 / 11 (compatible)

mbAgent compatibility

mbAgent debuts on Windows 10/11 + Chromium 140 and is the preferred runtime for browser-auto;
mbAgent is available on Windows 7 / legacy kernels, but browser-auto defaults to the candidate pages fallback;
mbAgent's release gate across 6 generations of Chromium (86 / 87 / 105 / 106 / 129 / 140) is in place, but the official writing capability is only declared after obtaining real evidence.

Installer SHA-256 and signature

Installer: AI_20260921_MBbrowserSetup_9.18.58.198_Core_140.exe
Verification tool: built into the upgrader; official website download page signature; command line Get-FileHash
Upgrade path: Consistent with historical versions such as v8.12.32.230 / v7.12.22.221 / v7.10.20.219; MBDATA is preserved; existing environments, fingerprints, Cookies, and pipeline are not touched

MBDATA data directory

Keep it on NVMe / SSD high-speed drives. Cookies, Local Storage, IndexedDB, User-Agent library, proxy database, login credentials, pipeline, and Start Menu templates all continue to read/write from MBDATA.

Version Summary

This v9.18.58.198 ApexCortex release is the starting point of Mbbrowser's transition from "browser tool" to "AI collaborative workspace".

Dimension	Upgrade Content
AI Engine	mbAgent debuts + browser-auto independent web automation engine
AI Models	DeepSeek + Claude + GPT three-tier official channels, Chat Completions + Responses dual protocols
AI Templates	130+ cross-border e-commerce Start Menu tasks, covering 15+ major categories
Mbbrowser Control Protocol	Control V2 persistent TCP + dual-controller fair queue + persistent idempotency + event stream backpressure
Mbbrowser New Features	Cookie expiry reminder email + embedded AI docs + multi-language + icon system
ApiServer	144 historical endpoints migrated to Control V2 + 4 local management endpoints + same spec as mbAgent
Client Experience	UI details, icons, scrolling, menu multilingual, window-close stability all polished

We recommend that all users engaged in cross-border e-commerce, multi-account matrices, ad placement, e-commerce store operations, and social media operations upgrade immediately after installing the same-kernel version. Before upgrading to the new version, please confirm the kernel version first (chrome://version); you must upgrade with the same kernel version number — otherwise, a kernel mismatch may create account credential loss risk. When necessary, users engaged in multi-account operations, cross-border business, social media matrices, ad placement, e-commerce store management, and automation workflows, after installing the same-kernel latest version, should not import all business data into the new version immediately. Gradually import a small number of environments into the new version, and only after testing stability can you proceed to broader safe use.

📥 Download This Update

Platform	Download
Windows 10 / 11 (Chrome 140 kernel, recommended)	MBbrowserSetup_9.18.58.198_Core_140.exe
Windows 10 / 11 (Chrome 129 kernel, compatible)	MBbrowserSetup_9.18.58.198_Core_129.exe

📢 For any usage questions, please contact official customer support for technical assistance.

Mbbrowser Official Technology Department

【March 11, 2026】Version: 7.12.22.221

Version: v7.12.22.221
Kernel Version: 140.0.7339.248 Build 20260311
Update Level: Major / Core Update Codename: "MigrationBridge"

Version Overview

This is the most anticipated update to Migratory Bird Fingerprint Browser since the product launched.

Previously, whenever you used Migratory Bird for overseas business operations, you couldn't escape a persistent headache: how do you make the browser go through a proxy? You had to wrestle with Proxifier in Windows, configure complex proxy rules exclusively for Migratory Bird's Chrome processes—and one wrong setting could cause proxy bypass failures or contaminate your entire system's network, affecting other programs.

All of that changes today.

This update introduces a groundbreaking core feature — the "Migratory Bird Upstream Proxy Bridge System (MBBridge)", a self-developed intelligent network proxy takeover engine that completely eliminates the long-standing pain of tedious and unstable upstream proxy configuration. Migratory Bird Fingerprint Browser is now free from dependency on third-party tools like Proxifier — configure once, works out of the box.

At the same time, this version also brings first-ever IPv6 international proxy support, 6x faster response speed, and numerous experience improvements, making this a truly comprehensive upgrade.

1. 🚀 Major New Feature: Upstream Proxy Bridge System (MBBridge)

📌 In one sentence: You used to need Proxifier to route Migratory Bird through a proxy. Now you don't.

What problem does this feature solve?

When Migratory Bird Fingerprint Browser opens each browser environment, it uses the Chrome engine under the hood. But how does the Chrome process route through a proxy? Previously, this required third-party tools like Proxifier to configure dedicated proxy rules for Chrome.

This approach had two pain points:

Required installing extra software with complex configuration;
Misconfiguration could cause proxy failures or pollute the network of other software.

MBBridge was created to internalize and automate this tedious process.

🎛 Where is the interface? How to open it?

Open Migratory Bird Fingerprint Browser, click the "Settings" icon in the bottom navigation bar, then click "Upstream Proxy" in the left menu to access the following interface:

MBBridge Upstream Proxy Settings Interface

⬆ The image above is the main configuration interface for MBBridge — clean and simple to use.

🔧 How to configure? Three steps

Step 1: Enter your proxy information

In the "Upstream Proxy Configuration" section:

Upstream Protocol: Select your proxy protocol from the dropdown — supports HTTP/HTTPS and SOCKS5;
Upstream Proxy: Enter the IP address and port provided by your proxy provider (e.g., 192.168.1.33 : 10808);
Username / Password: If your proxy requires account authentication, fill it in here; if using IP whitelist authentication, leave it blank.

Step 2: Click "Apply & Activate"

After filling in the details, click the "Apply & Activate" button — the system will immediately write your proxy configuration into the MBBridge engine.

You can also click "Test Connectivity" to verify that the proxy is working, and results will be shown in real time.

Step 3: Start the bridge

Click the "Start Bridge" button. The status indicator at the top of the interface will change from orange (not running) to green (running), indicating that MBBridge has successfully taken over the network traffic for all Migratory Bird browser environments.

From this moment on, every Migratory Bird browser environment you open will automatically route through your configured upstream proxy — no additional software configuration needed.

🔁 Two modes, flexible switching

MBBridge offers two outbound modes that you can freely choose based on your actual business scenario:

Mode	Use Case	Description
Proxy Mode (Recommended)	Running business with purchased proxy IPs	Migratory Bird browser process traffic routes through your configured upstream proxy server
Direct Mode (With Global VPN)	Users who have installed a global VPN on the system	Migratory Bird browser traffic routes directly through the OS VPN tunnel, no additional proxy config needed

💡 Most users should use "Proxy Mode". If you have V2Ray, Clash, or similar global VPN tools installed on your server, you can switch to "Direct Mode" and let MBBridge route through the system VPN.

🧠 How it works (plain English)

MBBridge runs in the background as a "system service daemon". After you click Start, it will:

Create a "virtual network adapter tunnel" on your computer (technically called a TUN virtual NIC);
Precisely identify Migratory Bird-related processes (chrome.exe, mbbrowser.exe, cdp.exe, etc.);
Automatically forward all network traffic from these processes through the virtual tunnel to your configured proxy server;
Non-Migratory Bird processes (such as QQ, WeChat on your computer) are completely unaffected, fully isolated.

What does this mean? — Precise process-level proxy isolation. Migratory Bird routes through the proxy; your other software accesses the internet normally, with no interference.

⚙ Bridge Control Buttons

Button	Function
Start Bridge	Enables proxy takeover — browser environments will route through the proxy
Pause	Temporarily pauses proxy takeover (background process is retained and can be resumed anytime) — for situations where you temporarily need to disable the proxy
Exit	Completely shuts down the MBBridge background process, fully stopping proxy takeover

📋 Usage Tips

MBBridge auto-starts every time you launch Migratory Bird Fingerprint Browser — no need to start it manually each time;
Proxy status is displayed in real time on the settings interface, so you can check current status at any time;
MBBridge has a built-in heartbeat monitoring mechanism — if the background process crashes unexpectedly, the Migratory Bird main program will automatically attempt to restart it, ensuring business continuity;
If you need to troubleshoot proxy issues, contact technical support to enable log mode — logs are saved to a local file for easy diagnosis.

2. 🔑 New Support: SSH Proxy Protocol (MBLink)

📌 In one sentence: Migratory Bird now natively supports SSH protocol proxying, with a built-in mblink.exe tool — use your SSH server as a proxy gateway with zero setup and zero extra installation.

What is SSH proxy? Who needs it?

SSH (Secure Shell) is an extremely common secure remote connection protocol. Many users have Linux servers or VPS instances — their SSH ports are a natural "proxy key": with just the server's domain/IP, username, and password (or key file), you can use that server as a proxy exit.

Previously, to use SSH proxy with Migratory Bird, you had to first establish a tunnel using PuTTY or XShell, then enter the local port into Migratory Bird's proxy settings — a cumbersome process, and if the tunnel dropped you had to reconnect manually.

Now, Migratory Bird has built the entire workflow in-house.

🛠 Core Tool: mblink.exe

A new program mblink.exe has been added to the Migratory Bird installation directory — this is Migratory Bird's self-developed SSH client engine, purpose-built for "proxy tunnel" scenarios.

Its main capabilities:

Capability	Description
Password / Key Dual Authentication	Supports both password login and private key file (.pem / .ppk format) authentication
Local Port Forwarding (-L)	Maps a remote server port to a local port, enabling a proxy tunnel
Dynamic SOCKS5 Forwarding (-D)	One-click turn any SSH server into a full-featured SOCKS5 proxy exit
Remote Port Forwarding (-R)	Exposes a local port to the remote server — ideal for intranet penetration
Script-Friendly	Supports non-interactive batch mode with standard exit codes, perfect for automation workflows
Heartbeat Reconnection	Automatically retries after unexpected tunnel disconnection, ensuring long-running business stability

🔒 Security

mblink.exe is implemented on Migratory Bird's self-developed SSH-2 protocol engine, strictly compliant with international standards (RFC 4251–4254). It enables the highest-security encryption algorithms by default (such as chacha20-poly1305, aes256-gcm), and supports automatic server fingerprint caching on first connection to prevent man-in-the-middle attacks.

All private key files, passwords, and session keys are managed securely in memory and immediately cleared after disconnection — nothing is left on disk.

📋 Typical Use Cases

Users with overseas VPS servers can use their VPS directly as a proxy exit, without purchasing commercial proxy IPs;
Enterprise intranet penetration: use SSH tunneling to let Migratory Bird access internal network systems;
Quick exit switching: when an existing proxy fails, spin up a backup SSH server immediately without interrupting business.

💡 How to use SSH proxy in Migratory Bird? When creating or editing a browser environment, select SSH as the proxy protocol, enter your server address, port (default 22), username, and password or key file path — Migratory Bird will automatically invoke mblink.exe in the background to establish a tunnel and take over that environment's traffic.

3. 🌐 First-Ever IPv6 International Proxy Support

📌 In one sentence: Migratory Bird can now use IPv6 proxies — you can purchase IPv6 proxy IPs for your business operations.

What is an IPv6 proxy? What are its advantages?

The global internet is transitioning from IPv4 (the traditional 4-segment format, e.g., 192.168.1.1) to IPv6 (the next-generation format, e.g., 2001:db8::1).

In many overseas markets (especially Europe, North America, and Japan), IPv6 proxy IPs are often cleaner than IPv4 for a simple reason: traditional industries and manual operations primarily use IPv4, while IPv6 address pools are enormous — the vast majority of IPs are "fresh" and have never been blacklisted by risk control systems.

In this update, Migratory Bird Fingerprint Browser fully supports IPv6 international proxies at the kernel level for the first time. You can now:

Purchase IPv6 proxy IPs from providers that support IPv6;
Enter your upstream proxy directly into Migratory Bird's "Upstream Proxy Configuration";
Fill in your purchased IPv6 proxy IPs directly in your environment configuration;
Enjoy cleaner IP resources for improved account security.

Applicable scenarios: Ideal for users operating cross-border e-commerce, social media management, or ad placement in regions with high IPv6 adoption such as Europe, the US, and Japan.

4. ⚡ Dramatically Faster Response — 6x Performance Improvement

We have refactored and enhanced key underlying core modules of Migratory Bird Fingerprint Browser — a performance optimization specifically targeting speed and stability.

What changes will you notice?

Environments open faster;
Switching browser windows feels smoother;
When bulk-launching multiple environments, overall speed is noticeably faster;
UI responses (button clicks, list loading) feel significantly more responsive.

Internal testing shows an average 6x improvement in overall client response speed. This isn't just a UI tweak — it's built from the ground up in the data processing pipeline, eliminating unnecessary redundant computations and blocking waits so Migratory Bird runs lighter and faster.

5. 🔕 New Default Setting: "Suppress Network Validation Failure Alerts"

Have you encountered this problem?

Sometimes while running business operations, Migratory Bird suddenly pops up a window — "Network Validation Failed" — interrupting whatever you're doing, and sometimes triggering an automatic edit window, forcing you to deal with the alert before continuing.

This typically happens when: the network momentarily fluctuates, the proxy server temporarily times out, or you're in the middle of switching proxy IPs. It's fundamentally just a transient network hiccup — it doesn't mean your environment configuration is wrong.

How does this update solve it?

A new global default setting has been added: "Suppress Network Validation Failure Alerts".

When this option is enabled (on by default):

When network validation briefly fails, Migratory Bird won't pop up a dialog to interrupt you;
The program silently retries in the background and automatically recovers when successful;
Configuration edit windows won't unexpectedly pop up due to network issues;
Overall business workflow is no longer interrupted by these non-critical alerts.

💡 When should you disable this option? If you're a new user who just configured a proxy and want to see all validation status feedback, you can manually turn this option off to see detailed validation results. During daily business operations, keep the default enabled.

6. 🏎 Faster Startup: Fixes Startup Freeze Caused by Network Drives

Problem Description

Some users reported: Migratory Bird Fingerprint Browser would freeze for several seconds to tens of seconds on certain servers or special computer environments before the interface appeared — as if the program had "locked up".

After in-depth investigation, we found the root cause: at startup, Migratory Bird used to check the available space on all disks (system call GetDiskFreeSpaceEx). This operation is harmless by itself — but if your computer has network-mapped drives (network drives such as NAS, SMB shares, or cloud drive mounts), checking those drives may require waiting for network responses, causing delays from 3–5 seconds up to tens of seconds.

Fix

Now when Migratory Bird starts, it automatically skips network drives and only checks local physical drives.

Effect of the fix:

On servers with network drives mounted, startup speed improves immediately and noticeably;
Completely eliminates the "startup freeze" caused by slow network drive responses;
No impact on regular users without network drives.

Particularly applicable: Users running Migratory Bird on cloud servers, VPS machines, or workstations with NAS or shared network drives will see a significant improvement in startup experience after upgrading.

Version Summary

This v7.12 update is the most important evolution of Migratory Bird Fingerprint Browser at the proxy infrastructure level.

The simultaneous launch of the MBBridge Upstream Proxy Bridge System and native SSH proxy capability (MBLink) marks a qualitative leap in Migratory Bird's proxy integration — whether you have commercial proxy IPs or your own SSH server, Migratory Bird can natively take over routing with a single click, completely eliminating the hassle of third-party tool configuration.

The addition of IPv6 proxy support gives Migratory Bird a broader and cleaner pool of IP resources in global markets.

Combine that with a 6x underlying performance improvement, startup freeze fix, and elimination of network validation interruptions — this is a milestone version that moves Migratory Bird from "workable" to truly "great". We strongly recommend all users upgrade immediately.

📥 Download This Update

Platform	Download
Windows 10 / 11 (Chrome 140 Kernel)	MBbrowserSetup_7.12.22.221_Core_140.exe

📢 For any questions, please contact official customer support or join the Migratory Bird official community group for technical assistance.

【February 06, 2026】Version: 7.10.20.219

Version: v7.10.20.219 Build 20260206 Update Level: Important/Core Update Codename: "DeepFlight"

Version Overview

This v7 update marks the most significant underlying change to Migratory Bird Browser in nearly half a year. In response to CloudFlare's increasingly stringent AI adversarial verification mechanism, particularly the TLS fingerprint recognition targeting mobile environments, we have introduced a brand-new adversarial logic at the kernel level. Simultaneously, we have conducted a deep retrospective to fix compatibility issues with outdated systems like Windows 7, and upgraded the Chrome 140 kernel to smooth out minor differences in the JS execution environment.

This update addresses a long-standing pain point for users: the inability to pass CloudFlare human verification when accessing high-security websites like pcmax.jp using iPhone simulation environments.

Official Download: Core 140 (Win10/11)

1. Core Breakthrough: Brand New "IphoneCloudFlare" Anti-Detection Mode

📌 Background and Challenge: The Wall of pcmax.jp

Over the past two months, we have received numerous feedback from VIP users. When attempting to log in to the Japanese popular dating website pcmax.jp using MBBrowser's iPhone 6/7/8/X/11/12 iOS profiles, they encountered unprecedented obstacles. CloudFlare's Turnstile verification exhibited extremely high interception rates in these mobile environments, reaching nearly 100% False Positive (false positive interception).

Specific symptoms: Users configured perfect MBBrowser commercial fingerprints and iPhone User-Agent, set matching screen resolutions (Retina), and even simulated TouchEvent. However, as soon as they opened pcmax.jp's login page, CloudFlare would enter an infinite verification loop or directly display "Access Denied".

📌 Deep Technical Attribution: The "Uncanny Valley" Effect of TLS Fingerprinting

Our core R&D team conducted in-depth analysis of data packets captured by the MbFireWall module for over 200 hours, and used Wireshark to compare network handshake packets between real iPhone devices (iOS 15-17) and MBBrowser simulation environments.

The conclusion was astonishing: the problem lies not in the application layer (HTTP Headers/JS), but in the transport layer (TLS/SSL).

When MBBrowser runs on Windows 10/11, underlying network requests call Windows' SChannel or OpenSSL libraries. The resulting TLS Client Hello data packets (containing Cipher Suites encryption suite lists, Extensions extension field order, Supported Groups, etc.) exhibit typical "IPHONE hardware parameter values inaccurate" characteristics.

CloudFlare's anti-scraping and risk control engines are extremely sensitive. They detected a logical paradox:

"This client claims to be an iPhone (User-Agent), its JavaScript environment also simulates iPhone, but its TLS handshake characteristics (JA3/JA4 Fingerprint) clearly tell the CloudFlare detection server—my iPhone data is not real enough."

This mismatch between application layer and transport layer characteristics directly triggers CloudFlare risk control, i.e., "Bot Fight Mode", causing pcmax.jp to not even give users the opportunity to display verification codes, directly determining suspected non-authentic IPHONE & suspected non-human operation.

📌 Solution: Global Setting "IphoneCloudFlare"

To solve this problem, we did not choose simple patches, but refactored the underlying network packet logic and introduced the "IphoneCloudFlare" option in global settings.

This also explains why our technical department performed extensive code commits in the MbFireWall and WinDivert module directories in the project (repeated testing and data drill comparison).

Technical Implementation Details:

Kernel-level Traffic Shaping
- When users check "IphoneCloudFlare" in global settings, MBBrowser activates the built-in Divert driver module
- This module runs in system kernel mode and can intercept all TCP/TLS handshake packets flowing to CloudFlare IP ranges
Dynamic TLS Fingerprint Spoofing
- When MbBrowser intercepts Client Hello packets, we no longer use OpenSSL's default generated structure, but perform byte-level reconstruction according to real iOS Safari TLS handshake characteristics
- Cipher Suites Reordering: Forcibly adjust the priority order of encryption suites to be completely consistent with iOS's Network.framework behavior, prioritizing mobile-specific suites such as TLS_AES_128_GCM_SHA256 and removing Windows-specific weak encryption suites
- Extension Padding: iOS Safari's padding method (Padding) for Extensions in Client Hello is completely different from Windows. The new feature precisely simulates this padding length and order
- ALPN (Application-Layer Protocol Negotiation): Forcibly specify h2 (HTTP/2) protocol negotiation order to match Safari's behavior
TCP/IP Protocol Stack Characteristic Simulation
- In addition to TLS, we also fine-tuned TCP layer characteristics (TTL value, Window Size)
- Windows' default TTL is usually 128, while iOS/Linux is usually 64
- IphoneCloudFlare mode automatically modifies outgoing packet TTL at the driver layer, making it appear more like it originates from a mobile device operating system when reaching the server

📌 Real-world Results

After stress testing by our internal testing team in 500+ clean IP environments:

Real-world Results

MBbrowser Client Settings Panel -> Browser Settings -> is not checked: The pass rate of the pcmax.jp login page is 0%.
MBbrowser Client Settings Panel -> Browser Settings -> is checked: The pass rate of the pcmax.jp login page has increased to 98.5% (the remaining 1.5% is due to issues with the IP's own blacklist).

This feature not only perfectly solves the pcmax.jp problem, but also fixes detection issues for other TLS fingerprint-sensitive websites (such as Nike, Ticketmaster, etc.) in mobile configuration environments.

2. Chrome 140 Kernel Sync and JS Display Consistency Fix

📌 Chrome 140 Kernel Upgrade

Following Google Chromium upstream updates, we have upgraded libcef and related rendering kernels to Chrome 140 version. This upgrade involves extensive header file and interface changes in the CDP (Chrome DevTools Protocol) directory.

Performance Improvement: V8 engine JavaScript execution efficiency improved by approximately 15%
New Feature Support: Support for latest CSS properties and Web APIs, ensuring the browser's "authenticity" keeps pace with mainstream browser versions

📌 Fix JS Display Inconsistency in iPhone Environment

In the old kernel version, when we used chromedp to simulate iPhone's viewport and devicePixelRatio, Chrome 140's new rendering pipeline had bugs when processing certain specific CSS Media Queries, causing some web pages (such as pcmax.jp's mobile version) to experience 1px displacement or overlap in the bottom navigation bar.

Although this has little impact on functionality, for extremely strict fingerprint detection scripts (determining whether it's a simulator through the difference between window.innerHeight and outerHeight), this is a fatal flaw.

Fix Content:

Modified CDP module's Emulation.setDeviceMetricsOverride call logic, adding height compensation for mobile status bars
Added deep Hook for window.screen object in MbCommand, ensuring that screen geometry information obtained at the JS layer is strictly consistent with CSS rendering results, eliminating this pixel-level fingerprint flaw

3. Compatibility Rollback: Go 1.20 and Win7 32-bit System Salvation

Although Windows 7 has been officially discontinued by Microsoft and only accounts for 8% of our user base, because some overseas businesses (particularly in Eastern Europe and Southeast Asia virtual machine environments) still heavily rely on lightweight Win7 32-bit systems, we must ensure their stability.

📌 Problem Symptoms

In the previous version, due to CDP compilation environment upgrade to Go 1.21, some system calls (Syscall) not supported by Win7 32-bit kernel were introduced, causing CDP service processes to silently crash when starting MBBrowser on this system, manifesting as blank pages or inability to connect to proxies.

📌 Fix Solution

Environment Downgrade and Conditional Compilation: We specifically built an independent compilation pipeline for the CDP module. When detecting the target system as Windows 7, the build script automatically switches to Go 1.20.14 version for compilation. Go 1.20 is the last version that perfectly supports Win7
This involves modifying build scripts in the CDP directory and performing compatibility rewrites (Polyfill) for code using Go 1.21 new features

4. Process Management Optimization: Farewell to "Zombie Chrome"

📌 Problem Description

Users reported that after closing the MBBrowser main program on Windows 7, underlying chrome.exe child processes sometimes don't exit accordingly, but become "zombie processes" residing in the background, occupying 200MB+ memory. If users frequently open and close browsers, this can lead to system memory exhaustion and freezing.

📌 Technical Analysis

This is not related to UseAfterFree, but rather an IPC (Inter-Process Communication) signal loss issue. On Win7, when the parent process (UI process) forcefully ends via TerminateProcess, Chrome child processes cannot receive exit instructions through Named Pipe.

📌 Fix Measures

Job Object Binding
- We introduced Windows' Job Object mechanism in MbCommand's process startup logic
- Modified code automatically adds all launched chrome.exe child processes to an independent Job Object
- Even if the main program crashes unexpectedly or is forcefully terminated, the operating system guarantees all child processes in the Job Object are terminated together
- This is system-level lifecycle management, completely solving the zombie process problem

5. Installation Package Experience Optimization: Version Number Directory Normalization

📌 Problem Description

In the original SetupInstall logic, the installation package's default extraction path was usually fixed (e.g., C:\Program Files\MBBrowser). This caused great inconvenience for users when conducting version comparison tests or multi-version coexistence, requiring manual folder renaming.

📌 Optimization Content

Version-Aware Install Path: Modified NSIS installation scripts; now the installer automatically reads the current build version number (Version Info)
Default installation path changed to C:\Program Files\MBBrowser_v7.10.20.219
Also updated uninst.exe generation logic, ensuring the uninstaller correctly identifies and cleans version-numbered directories without mistakenly deleting coexisting files of other versions
This greatly facilitates studio users for gray release and rollback testing

6. Java Environment Download Fix: Breaking Cache Deadlock

📌 Problem Background

Some advanced plugins of MBBrowser depend on Java Runtime Environment (JRE). On Windows 7 systems, when the downloader attempts to update JRE, due to Win7's aggressive WinINet caching policy, even if the server releases a new JRE package, the client would repeatedly download locally cached old files, causing checksum failures (Hash Mismatch) and infinite retries.

📌 Fix Solution

Forced Pass-through (Cache Busting)
- Forcibly added Cache-Control: no-cache and Pragma: no-cache to HTTP request headers in the download module
URL Randomization: To bypass stubborn man-in-the-middle proxy caches (ISP Cache), we appended random timestamp parameters ?t=TIMESTAMP to download URLs
This fix has been verified and completely solves the problem of Java environment updates getting stuck at 99% on Win7

Version Summary

Although this v7 update appears unremarkable on the surface, it contains significant underlying changes. Particularly with the launch of the "IphoneCloudFlare" feature, MBBrowser has achieved decisive victory in combating "TLS fingerprinting" in the deep waters of the anti-scraping domain.

We recommend all users engaged in Japanese e-commerce and social businesses (pcmax, tinder, etc.) to upgrade immediately and enable this option.

Official download link: Chromium 140 Kernel Version (Compatible with Windows 10/11)

2026 Version Updates ​

【October 26, 2026】Version: 9.58.18.206 ​

Overview ​

Find the changes that matter to you ​

1. 🧭 Group control: Get organized before you get to work ​

Windows wait until they are ready, then move into place ​

Find group history and settings more easily ​

2. 📝 Reusable text groups: Prepare it once and find it again ​

What has changed? ​

3. 🧰 Script setup: See what is missing before you install it ​

From “it will not run” to “I know what to do next” ​

4. 🤖 MbAgent: Follow what the AI is doing ​

Clear task states and options you can select ​

Prepare browser automation when you need it ​

Find templates, project details, and account usage ​

5. 🪟 Windows and interface: A little more polish in everyday use ​

6. 🔄 Support for new and older browser cores ​

Group control continues to improve on older cores ​

Proxy, startup, and shutdown behavior is more reliable ​

7. ✨ Start with the step that slows you down most ​

8. 📥 Download version 9.58.18.206 ​

Read before upgrading ​

1. Know the difference between the software version and browser core ​

2. Back up first, then test with a small number of environments ​

3. Choose an installer that fits your Windows version and needs ​

4. Follow the prompts the first time you run a script or AI task ​

【September 21, 2026】Version: 9.18.58.198 ​

Version Overview ​

1. 🧭 Major Debut: mbAgent — Mbbrowser's Native AI Agent ​

What problem does this feature solve? ​

What can mbAgent do for you? ​

How does it do all this? — Its relationship with Mbbrowser ​

2. 🚀 Brand-New Independent Engine: browser-auto (Mbbrowser Web Automation Engine) ​

Why does it need to be an independent engine? ​

Relationship with mbAgent native page tools (candidate pages) ​

The difference you will feel ​

3. 🌐 Brand-New Official AI Model Channels: DeepSeek + Claude + GPT ​

What problem does it solve? ​

Chat and Responses both supported ​

Model categories and membership tiers ​

Audit and redaction ​

4. 🎨 Brand-New "Start Menu": 130+ Cross-Border E-Commerce Task Templates ​

What is this for? ​

Highlights ​

5. 🤖 ApiServer and mbAgent Dual-Controller Coexistence ​

What problem does this mechanism solve? ​

Actual usage ​

The mbAgent capability ledger ​

6. 🍪 mbbrowser Cookie Expiry Reminder Email (New Feature) ​

What is this for? ​

How does Mbbrowser help? ​

Key details ​

Important notice ​

7. 🔁 mbbrowser Client: Control V2 Dual-Controller Protocol Fully Enabled ​

What is Control V2? ​

Details of mbAgent integration ​

Start and stop ​

Compatibility ​

8. 🛡 Security / Efficiency Improvements You Will Feel Immediately ​

✅ UI improvements you will see ​

✅ Features you will feel directly ​

✅ Background operations improvements ​

9. 📚 Companion Action: Mbbrowser Official Documentation Synced ​

Client embedded documentation ​

Help documentation site ​

10. ⚙ Read Before Upgrading ​

Same-kernel version is mandatory ​

Built-in browser kernel (Chromium) ​

mbAgent compatibility ​

Installer SHA-256 and signature ​

MBDATA data directory ​

Version Summary ​

Mbbrowser Official Technology Department ​

【March 11, 2026】Version: 7.12.22.221 ​

Version Overview ​

1. 🚀 Major New Feature: Upstream Proxy Bridge System (MBBridge) ​

What problem does this feature solve? ​

🎛 Where is the interface? How to open it? ​

🔧 How to configure? Three steps ​

🔁 Two modes, flexible switching ​

2026 Version Updates

【October 26, 2026】Version: 9.58.18.206

Overview

Find the changes that matter to you

1. 🧭 Group control: Get organized before you get to work

Windows wait until they are ready, then move into place

Find group history and settings more easily

2. 📝 Reusable text groups: Prepare it once and find it again

What has changed?

3. 🧰 Script setup: See what is missing before you install it

From “it will not run” to “I know what to do next”

4. 🤖 MbAgent: Follow what the AI is doing

Clear task states and options you can select

Prepare browser automation when you need it

Find templates, project details, and account usage

5. 🪟 Windows and interface: A little more polish in everyday use

6. 🔄 Support for new and older browser cores

Group control continues to improve on older cores

Proxy, startup, and shutdown behavior is more reliable

7. ✨ Start with the step that slows you down most

8. 📥 Download version 9.58.18.206

Read before upgrading

1. Know the difference between the software version and browser core

2. Back up first, then test with a small number of environments

3. Choose an installer that fits your Windows version and needs

4. Follow the prompts the first time you run a script or AI task

【September 21, 2026】Version: 9.18.58.198

Version Overview

1. 🧭 Major Debut: mbAgent — Mbbrowser's Native AI Agent

What problem does this feature solve?

What can mbAgent do for you?

How does it do all this? — Its relationship with Mbbrowser

2. 🚀 Brand-New Independent Engine: browser-auto (Mbbrowser Web Automation Engine)

Why does it need to be an independent engine?

Relationship with mbAgent native page tools (candidate pages)

The difference you will feel

3. 🌐 Brand-New Official AI Model Channels: DeepSeek + Claude + GPT

What problem does it solve?

Chat and Responses both supported

Model categories and membership tiers

Audit and redaction

4. 🎨 Brand-New "Start Menu": 130+ Cross-Border E-Commerce Task Templates

What is this for?

Highlights

5. 🤖 ApiServer and mbAgent Dual-Controller Coexistence

What problem does this mechanism solve?

Actual usage

The mbAgent capability ledger

6. 🍪 mbbrowser Cookie Expiry Reminder Email (New Feature)

What is this for?

How does Mbbrowser help?

Key details

Important notice

7. 🔁 mbbrowser Client: Control V2 Dual-Controller Protocol Fully Enabled

What is Control V2?

Details of mbAgent integration

Start and stop

Compatibility

8. 🛡 Security / Efficiency Improvements You Will Feel Immediately

✅ UI improvements you will see

✅ Features you will feel directly

✅ Background operations improvements

9. 📚 Companion Action: Mbbrowser Official Documentation Synced

Client embedded documentation

Help documentation site

10. ⚙ Read Before Upgrading

Same-kernel version is mandatory

Built-in browser kernel (Chromium)

mbAgent compatibility

Installer SHA-256 and signature

MBDATA data directory

Version Summary

Mbbrowser Official Technology Department

【March 11, 2026】Version: 7.12.22.221

Version Overview

1. 🚀 Major New Feature: Upstream Proxy Bridge System (MBBridge)

What problem does this feature solve?

🎛 Where is the interface? How to open it?

🔧 How to configure? Three steps

🔁 Two modes, flexible switching