black-ant/Ant-Browser

Overview

Ant Browser is a desktop application that manages multiple independent browser instances on one machine. Each instance gets its own browser profile and can be bound to a dedicated proxy, which makes it suited to multi-account operations such as cross-border e-commerce and social media account management, isolated proxy testing, and teams that need consistent browser kernel and instance configuration. Configuration and runtime data stay local.

Beyond instance creation and start/stop, the app includes a proxy pool with Clash import and latency/IP health checks, browser kernel version management, tag/keyword filtering, a Ctrl + K quick launcher keyed by instance Code, automation script packages, plugin management, ZIP-based instance migration, and backup to local, OpenList, or S3.

Getting started

1. Download and install the latest build from Releases: run AntBrowser-Setup-*.exe for the Windows installer, unpack and run ant-chrome.exe for the portable build, install the .deb or unpack ant-chrome on Linux, or open the macOS .app (unsigned internal build).
2. If macOS Gatekeeper blocks the app, the README instructs running xattr -dr com.apple.quarantine <app-path> on the local test package before opening it.
3. Open 指纹浏览器 > 内核管理 and use the in-app download to prepare a Chromium kernel, or place a kernel directory containing chrome.exe manually. A matching fingerprint Chromium source is recommended in fingerprint-chromium.
4. Under 代理池配置, add or import proxy nodes and check latency and health.
5. Under 实例列表, click 新建配置, set name, kernel, proxy, tags, and launch parameters, then start the instance.
6. Open an IP-check site inside the instance to confirm the exit IP, region, ASN, and risk values.

To build from source on Windows, use bat\dev.bat (add live for Vite hot reload or limited for a memory-capped watcher); Linux uses ./scripts/dev.sh. Release packaging is handled by scripts under publish/linux/ and publish/mac/.

Constraints

• Supported platforms are 64-bit Windows 10/11, Linux amd64/arm64, and macOS amd64/arm64; the macOS package is currently unsigned and aimed at internal testing.
• About 8 GB of memory and 2 GB of disk space are suggested, and instance data is stored locally per user.
• Proxy connectors are split into two stacks, xray (Xray plus sing-box) and mihomo; the app does not automatically mix them, so switching stacks requires re-testing. Details are in the proxy protocol audit.
• Backup credentials for OpenList and S3 are stored in backup.local.yaml in the user config directory and should not be committed or copied into public repositories.
• The source is licensed under PolyForm Noncommercial License 1.0.0, which permits non-commercial use only; commercial use is outside the license scope.

HotRepo's take

The repository first appears in HotRepo's Go daily list on 2026-11-15 at 14th place with 10 new stars that day, on a base of 2,184 stars and 358 forks. That is a single snapshot, not a trend: there is no multi-day series to show whether the growth is sustained. For a desktop browser tool with a proxy pool, backup, and automation surface, the technical scope in the README is broad and concrete, but the delivered binaries are unsigned on macOS and the README does not document how release artifacts map to the source tree. This makes the project better suited to users who can verify the build themselves, rather than those who need a vetted, signed distribution.