Browser3 149.0.7827.201 r3
A multi-profile antidetect Chromium browser for people and AI agents.
Browser3 implements native Chromium-level fingerprint masking while keeping its primary differentiator: Persistent, internally consistent browser identities.
What is new in r3
- The verified TASK-005 v4 GIF and MP4 demo and the dated public validation report are synchronized with this release.
- First run is available through the one-command Windows wrapper:
.\browser3. - The package now includes the loopback-only
browser3_agent.pySession API for supported Playwright, Puppeteer, and custom automation clients. - FAQ, usage, release notes, public-source boundary, and distributed files now describe the same shipped capabilities.
Current release validation
The 2026-08-20 headful, CDP-free Release gate ran without a proxy across all five profiles. All five returned scores and reload measurements. The five-profile averages were:
tampering_ml_score: 0.0412virtual_machine_ml_score: 0.0654- optional
vpn_ml_score: 0.1250
These are dated observations on the stated host and release, not a guarantee of future detector results or bypass. Proxy and multi-geo operation are not part of this release's tested GO.
Install
- Download
Browser3-149.0.7827.201-windows-x64.zip. - Verify it with the signed checksum manifest below.
- Extract the complete archive on Windows 10/11 x64.
- Run
.\browser3.
Python 3.7 or newer must be available through py.exe -3 or python.exe. Keep the complete runtime\ directory intact. A physical hardware-accelerated GPU is required.
Authenticity
Browser3 PE files are not Authenticode-signed. Do not disable SmartScreen or antivirus protection. Verify the detached OpenPGP signature instead:
gpg --import browser3-release-key.asc
gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt
Get-FileHash -Algorithm SHA256 Browser3-149.0.7827.201-windows-x64.zipRelease-key fingerprint:
138A E853 7368 8ADF FDD0 05A2 7439 B75B E864 5184
The release contains exactly six uploaded assets. GitHub's automatically generated source archives are not installers and are not covered by SHA256SUMS.txt.
Known limits
- Windows x64 only; Widevine is not included.
- Profiles are generated for the current physical machine and should not be moved to different hardware.
- Enabling CDP can cause detector dashboards to report Developer Tools.
- Network-risk observations depend on proxy/IP reputation and changing detector behavior.
- The public source snapshot is MPL-2.0 orchestration and documentation source; it cannot build the proprietary Browser3 executable.