timethrough/xiaohei-chrome — explained in plain English
Analysis updated 2026-05-18
Run several isolated Chrome profiles side by side without cookies or cache leaking between them.
Check a proxy's exit IP and test compatibility before using it across separate browser profiles.
Manage and sync browser extensions and windows across multiple local environments.
| timethrough/xiaohei-chrome | elyelysiox/recaptcha | gaearon/react-deep-force-update | |
|---|---|---|---|
| Stars | 122 | 122 | 121 |
| Language | JavaScript | JavaScript | JavaScript |
| Setup difficulty | moderate | easy | easy |
| Complexity | 3/5 | 5/5 | 2/5 |
| Audience | general | researcher | developer |
Figures from each repo's GitHub metadata at analysis time.
Portable build still requires a separately installed copy of Google Chrome, building from source needs Node.js, npm, and a .NET Framework 4 C# compiler.
xiaohei-Chrome, whose project name translates roughly to Xiaohei Multi-Instance Launcher, is a tool for running many separate, isolated Chrome browser profiles on the same Windows computer. The project's README notes that its code was mainly written and maintained by ChatGPT under the guidance of the project's user, and asks anyone running it to review the source themselves and scan it with trusted antivirus or sandbox tools before use, since automated AI review is only a helper and not a full security audit. The current release is version 14.0.0, and its focus is local isolation between browser environments. Each environment gets its own Chrome user directory, so cookies, cache, local storage, and IndexedDB data stay separate from one profile to the next. The tool also supports standard browser privacy settings, checking a proxy's exit IP, compatibility testing, managing browser extensions, and syncing windows across profiles, along with diagnostics for keeping environments consistent. The README is explicit that the tool does not promise to help users evade a website's risk controls, anti-bot systems, or account linking detection. It also states that the app does not upload browser profiles, cookies, proxy credentials, logs, or any third-party executables to a remote server, since configuration and user data are kept on the local machine by default. Most users are expected to download a portable Windows build from the project's GitHub Releases page, unzip it fully, and run a START command file. That build bundles Electron and a matching Chromium runtime, though a separately installed copy of Google Chrome is still required for the browser environment features to work. Building the portable package from source instead requires Windows 10 or 11, Node.js, npm, a .NET Framework 4 C sharp compiler, and Google Chrome, and involves running npm commands that recompile several native helper programs and download a locked Electron version before packaging the final zip file.
A Windows tool that runs many isolated Chrome browser profiles side by side, each with its own cookies, cache, and storage.
Mainly JavaScript. The stack also includes JavaScript, Electron, Node.js.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly general.
This repo across BitVibe Labs
Verify against the repo before relying on details.