docs: changelog 2026-08-14, release 151.0.7922.76 with per-context UDP proxy control

Author: MSTU0

CHANGELOG.md

@@ -3,6 +3,20 @@
 > **Research scope:** Entries in this changelog describe features evaluated in authorized labs and defensive benchmarking programs. Follow the [Legal Disclaimer](DISCLAIMER.md) and [Responsible Use Guidelines](RESPONSIBLE_USE.md). We work with security vendors to investigate any misuse, so report concerns to [support@botbrowser.io](mailto:support@botbrowser.io).
 
 
+## [2026-08-14]
+### Major
+- **Chromium Core -> 151.0.7922.76**: Updated the BotBrowser 151 release line with upstream Web Platform, rendering, and security updates.
+
+### New
+- **Per-Context UDP Proxy Policy (`--bot-udp-proxy`)**: Added per-context control over UDP proxy and HTTP/3 handling, so sibling browser contexts sharing one profile can independently opt in or out.
+
+### Improvements
+- **Timezone and Geolocation Consistency**: Improved profile-backed timezone and location alignment across pages, workers, and browser contexts when routing through proxies.
+- **Cross-Platform Font Consistency**: Improved font metric consistency for browser-family profiles running across host platforms.
+- **Per-Context Consistency**: Improved per-context fingerprint identity consistency.
+- **Server Stability**: Improved stability on servers without dedicated graphics hardware.
+
+
 ## [2026-08-03]
 ### Major
 - **Chromium Core -> 151.0.7922.47**: Updated the BotBrowser 151 release line with upstream Web Platform, rendering, and security updates.

CLI_FLAGS.md

@@ -58,6 +58,7 @@ Each entry shows availability and the primary guide. The guide documents startup
 
 - [`--proxy-server`](#flag-proxy-server) (Core; Context/Live ENT Tier3): [Proxy Configuration](docs/guides/network/PROXY_CONFIGURATION.md)
 - [`--disable-quic`](#flag-disable-quic) (Standard Chromium): [UDP over SOCKS5](docs/guides/network/UDP_OVER_SOCKS5.md)
+- [`--bot-udp-proxy`](#flag-bot-udp-proxy) (ENT Tier3): [UDP over SOCKS5](docs/guides/network/UDP_OVER_SOCKS5.md)
 - [`--proxy-pac-url`](#flag-proxy-pac-url) (Core PAC; callback ENT Tier3): [PAC Request Policy](docs/guides/network/PAC_REQUEST_POLICY.md)
 - [`--proxy-ip`](#flag-proxy-ip) (ENT Tier1): [Proxy and Geolocation](docs/guides/network/PROXY_GEOLOCATION_ALIGNMENT.md)
 - [`--proxy-bypass-rgx`](#flag-proxy-bypass-rgx) (PRO): [Proxy Selective Routing](docs/guides/network/PROXY_SELECTIVE_ROUTING.md)
@@ -240,6 +241,20 @@ To keep SOCKS5 proxying but avoid QUIC/HTTP/3, add the standard `--disable-quic`
 
 `--disable-quic` affects QUIC/HTTP/3 only. WebRTC/STUN behavior still follows the UDP-over-SOCKS5 and WebRTC settings.
 
+<a id="--bot-udp-proxy-ent-tier3"></a>
+<a id="flag-bot-udp-proxy"></a>
+### `--bot-udp-proxy` (ENT Tier3)
+Set the UDP proxy and HTTP/3 policy for a single browser context. Sibling contexts that share one profile can keep it on for one context and off for another, without taking the whole browser process off QUIC with `--disable-quic`.
+
+```bash
+# Bare flag means true
+--bot-udp-proxy
+--bot-udp-proxy=true
+--bot-udp-proxy=false
+```
+
+Supply it on the main command line for a process-wide default, or through Per-Context Fingerprint when a context should override that default. A context inherits the main-process value when it does not set its own, and the policy can be switched after the context is created. This flag applies only to profiles that already carry the UDP entitlement and never grants the capability on its own. Process-level `--disable-quic` still takes priority. See [UDP over SOCKS5](docs/guides/network/UDP_OVER_SOCKS5.md).
+
 <a id="pac-request-policy-ent-tier3"></a>
 <a id="pac-like-request-callback-ent-tier3"></a>
 ### PAC-Like Request Callback (ENT Tier3)

docs/guides/network/UDP_OVER_SOCKS5.md

@@ -96,6 +96,17 @@ Use the standard `--disable-quic` flag when you want HTTP traffic to stay on TCP
 
 This disables QUIC/HTTP/3. It does not disable WebRTC or STUN; those continue to follow your UDP-over-SOCKS5 and WebRTC settings.
 
+### Per-context UDP policy (ENT Tier3)
+
+When several browser contexts share one profile, use `--bot-udp-proxy` to keep UDP proxy and HTTP/3 on for some contexts and off for others in the same browser process. A bare flag means true.
+
+```bash
+--bot-udp-proxy=false   # process-wide default for this profile
+--bot-udp-proxy=true    # per-context override through Per-Context Fingerprint
+```
+
+Set the process default on the main command line, then override it per context through Per-Context Fingerprint. Unlike `--disable-quic`, which takes the whole process off QUIC, this policy stays scoped to the context that sets it. It applies only to profiles that already carry the UDP entitlement.
+
 ### When the proxy does not support UDP
 
 If the proxy does not support UDP ASSOCIATE, BotBrowser falls back gracefully:

profiles/stable/README.md

@@ -4,7 +4,7 @@ BotBrowser 150 and newer profiles are delivered through subscription or support
 
 | Release line | Matching BotBrowser build | Profile files |
 |--------------|---------------------------|---------------|
-| v151 | 151.0.7922.47 | Subscription profiles: [support@botbrowser.io](mailto:support@botbrowser.io), [@botbrowser_support](https://t.me/botbrowser_support) |
+| v151 | 151.0.7922.76 | Subscription profiles: [support@botbrowser.io](mailto:support@botbrowser.io), [@botbrowser_support](https://t.me/botbrowser_support) |
 | v150 | [150.0.7871.182](https://github.com/botswin/BotBrowser/releases/tag/150.0.7871.182) | Subscription profiles: [support@botbrowser.io](mailto:support@botbrowser.io), [@botbrowser_support](https://t.me/botbrowser_support) |
 | v149 | [149.0.7827.200](https://github.com/botswin/BotBrowser/releases/tag/149.0.7827.200) | Legacy public demo files: `chrome149_*.enc`, `webkit26_*.enc` |
 | v148 | [148.0.7778.97](https://github.com/botswin/BotBrowser/releases/tag/148.0.7778.97) | Legacy public demo files: `chrome148_*.enc` |