vibatchium

Name: vibatchium
Author: trueoriginlabs

作者：trueoriginlabs版本 0.21.0i★ –i在你的电脑上运行

注册名称io.github.trueoriginlabs/vibatchium

安装

概览

作者提供的说明（英文原文）

Stealth browser automation for AI agents — real Chrome, N parallel persistent logged-in sessions.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 网页与浏览器

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "vibatchium": {
      "command": "uvx",
      "args": [
        "vibatchium",
        "mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add vibatchium -- uvx vibatchium mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "vibatchium": {
      "command": "uvx",
      "args": [
        "vibatchium",
        "mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "vibatchium": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "vibatchium",
        "mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 trueoriginlabs 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“网页与浏览器”中的其他服务器比较i

星标数多于此分类中其他 879 个服务器的 0%
发布到注册中心的时间比此分类中其他 879 个服务器的 97% 更新
基础检查结果等于或优于此分类中其他 879 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

vibatchium 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.21.0）于昨天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Browser Use, Chrome DevTools MCP, MCP Server Browser

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Browser Use

作者：browser-use

Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.

电脑或云端★ 120,087MIT17天前更新

安装

Chrome DevTools MCP

作者：ChromeDevTools

MCP server for Chrome DevTools

在你的电脑上运行★ 54,821Apache-2.015天前更新

安装

MCP Server Browser

作者：bytedance

MCP server for browser use access

在你的电脑上运行★ 39,550Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

vibatchium

The browser layer for an always-on box. Many logged-in identities, running unattended, all at once — on real Chrome, with stealth on by default, and with a security model for letting an AI near the credentials.

One daemon, N persistent Chrome sessions, a vb CLI and an MCP server. Self-hosted, free, Apache-2.0.

pipx install 'vibatchium[all]'

patchright install chrome vb setup # register the MCP server + agent skill (Claude Code, Codex, Cursor) vb explore https://example.com

Is this for you?

You want…	Use
An agent driving your signed-in browser while you watch	Claude in Chrome, Chrome Auto Browse — first-party, free, better integrated
The stealthiest single browser you can buy	CloakBrowser — fingerprints patched in Chromium's C++ (paid for concurrency)
The leanest driver for one agent	bladebro — five tools, one Rust binary
Browser automation without anti-bot pressure	playwright-mcp, agent-browser — bigger, older, better tested
Many accounts on one box, running unattended, against sites that fight automation	vibatchium

That last row is the whole wedge. Supervised agents hand control back to you at every login wall and CAPTCHA; a library leaves the fleet — sessions, budgets, crash recovery, credentials — for you to build. vibatchium is that fleet layer.

How it compares

As of 2026-10-06, from each project's own README, source and release notes (the MCP-cost row is our own measurement¹). Rows where we lose are included on purpose.

	vibatchium	CloakBrowser	bladebro	agent-browser	playwright-mcp
N persistent logged-in sessions at once	yes, free, one daemon	1 free (latest build) · more on Pro	one Chrome per agent session	yes, one daemon per session	one per profile dir
Unattended ops: crash self-heal, leases, budgets, idle freeze, goals	all of them	—	partial (crash relaunch, idle timeout)	partial (idle timeout, restore)	idle timeout
Agent can use a secret but not read it (origin-bound fill, read-back refused, TOTP)	yes	—	—	vault, origin check	`--secrets` redaction
Prompt-injection scanning of page content	yes	—	—	boundary markers (opt-in), no scanning	—
Browserless HTTP on the session's own cookies, Chrome TLS fingerprint · keyless web search	yes	—	—	—	—
Browser	stock Chrome	own Chromium build	stock Chromium	Chrome for Testing default	stock Chrome
Stealth layer	CDP-level (Patchright)	engine-level (87 C++ patches)	CDP-level ("6-layer"), no `Runtime.enable`	none in core; via cloud providers	none
Published stealth score	not yet	30/30 on its own detector list	68/80 Stealth Bench V1 (self-run)	—	—
MCP startup cost in Claude Code¹	~2.7k tokens (89 tools, 5 always loaded)	n/a	~3.4k tokens (5 tools)	not measured	not measured
Platforms	Linux (macOS: CI probe, unsupported)	Linux · macOS · Windows	Linux · macOS · Windows	all	all

¹ bytes/4 of tools/list plus server instructions, measured over stdio. Clients without tool search load every tool: vb mcp --caps min is 12 tools, ~3.8k tokens. bladebro's own README says ~1.9k.

Where the others are genuinely better: CloakBrowser's engine-level patches go deeper than any CDP-level layer can — and vb start --browser-binary will drive a Chromium build you bring. bladebro has a stealth benchmark number and we don't; until we do, read our stealth claims as measured on scoreboards, below, not on production walls. Both run on more operating systems.

What only vibatchium does

1. A fleet of logged-in identities on one box. Each session is its own Chrome and profile, with its own proxy, timezone and GPU node, and — opt-in with vb persona set — its own screen and window, because by default every headless session on one machine reports the same 800×600 screen. vb fleet-check measures how alike your sessions still look. They run in parallel on one daemon that keeps them alive: a crashed renderer is relaunched on the same profile, parked sessions have their renderers stopped and thawed on the next call, leases stop two agents clobbering one session, and goals give a task a step/spend/time budget that survives a daemon restart.

vb --session alice start && vb --session alice go https://x.com      # log in once, stays logged in

vb --session bob start && vb --session bob go https://x.com vb --session alice act "open notifications" & vb --session bob extract & wait vb fleet-check --sessions alice,bob # how twinned are they?

2. Credentials an agent can use but never see. The vault fills a password or a live TOTP code into the page without the value reaching the model's context, a screenshot or a log — and only into the site it belongs to. Over MCP, a prompt-injected agent can't type your GitHub password into a lookalike page, can't read it back with value or eval while it sits in the field, and can't edit the vault or pull a code. An agent with a *shell* is the operator — the CLI has deliberate escape hatches — so give agents MCP, not Bash, if that boundary matters to you.

printf %s "$GH_PASSWORD" | vb secret set github.com password --stdin

printf %s "$GH_TOTP_SEED" | vb secret set github.com totp-seed --stdin vb --session work fill @e7 --use-secret github.com:password vb --session work fill @e9 --use-secret github.com:totp vb wait-email-code github.com # operator CLI: polls IMAP and prints the code; refused over MCP

3. Page text is treated as untrusted. Every session scans the page text it returns for instructions aimed at the agent and flags them by default; wrap fences them off and redact removes them. Caller-supplied file paths are confined too, so an injected agent can't upload ~/.ssh or write into .git/hooks.

4. A browserless lane on the same identity. vb fetch reuses a session's cookies and proxy with Chrome's TLS fingerprint and client hints — JSON endpoints behind your login at curl speed, and it tells you when it can't match the browser. vb search finds URLs with no API key and no per-session budget.

vb --session work fetch https://api.example.com/v1/me

vb search "site reliability postmortem" -n 20 --urls

Status: alpha, active development. 2,331 tests green in CI (Linux, Python 3.11–3.14). Coding agents: read AGENTS.md first — the one-call recipes and the traps worth skipping.

Detector scores quoted below (bot.sannysoft, CreepJS, Cloudflare cold-launch) are manual observations, not CI-asserted — no test in the suite gates on them, and they are only as current as the last hand-run. The generated block under Measured scores is the one to trust.

Install

pipx install vibatchium             # core: browse / extract / screenshot / N parallel sessions

pipx install 'vibatchium[all]' # + fetch/search lanes, credential vault, VLM read, REST shim

(or pick extras: [fetch], [secrets], [llm], [rest])

patchright install chrome vb setup # register MCP + an auto-discoverable skill (idempotent) vb install # report which optional lanes are available

On a uv venv (no pip), add an extra with uv pip install --python /bin/python curl_cffi. Bleeding edge from master: pipx install 'git+https://github.com/trueoriginlabs/vibatchium#egg=vibatchium[all]'.

Install as a skill / plugin

vb setup wires up the agents on *this* machine. To pull just the agent skill into any agent skills.sh supports (Claude Code, Codex, Cursor, Gemini CLI, Copilot, …), or to install skill + MCP server as one Claude Code plugin:

npx skills add trueoriginlabs/vibatchium                  # skill only, any agent

/plugin marketplace add trueoriginlabs/vibatchium # Claude Code: skill + vb mcp /plugin install vibatchium@vibatchium

Both still need the vb CLI on PATH (pipx install 'vibatchium[all]') — the skill drives it and the plugin's MCP server *is* vb mcp. On Claude Code, pick the plugin or vb setup, not both, or you register the server twice. The skill file is generated from vibatchium/setup_cmd.py; edit there and run python scripts/sync_skill.py.

Quick start

vb explore https://example.com                      # one call: text-first, auto-closes

vb research --target https://example.com \ # parallel fan-out, N intents --intent "pricing model" --intent "customers" --intent "tech stack"

Real Chrome vs fake Chrome

A wave of "headless browser for AI agents" tools rebuild the browser from scratch (Rust + V8, no Blink/Skia) to hit tiny memory and sub-100ms page loads. The catch is structural: with no rendering engine, they can't produce a real device's fingerprint — they synthesize one. And synthetic fingerprints don't hold still.

vibatchium drives *real* Google Chrome, so its fingerprints are real — and, more to the point, stable. The single test that separates the two is fingerprint stability across navigations. Run the same canvas + WebGL probe on two pages in one session:

	vibatchium (real Chrome)	synthesized-fingerprint engines
canvas hash, page A → page B	identical	reseeded per navigation
WebGL `readPixels`	real, deterministic pixels	often `Math.random()`
WebGL renderer	a real ANGLE renderer¹	stub / zeros

¹ Chrome's own software renderer (SwiftShader) by default — still a coherent, deterministic Chrome value, not a stub. A hardware-GPU string (e.g. ANGLE (Intel …)) needs the opt-in --gpu flag.

A real device returns the same fingerprint every page load; a fingerprint keyed off Date.now() does not — and *that inconsistency* is exactly what lie-detection fingerprinters (CreepJS and friends) flag. Measured: vibatchium's canvas hash and WebGL readback are byte-identical across navigations, and CreepJS reported 0 % stealth-tampering (no synthetic-environment signatures) when last run by hand. That figure is not regression-tested — treat it as an observation, not a guarantee.

This is not a claim of invisibility. The moat is fingerprint *authenticity*, not hiding that a browser is automated — vibatchium still reads as headless on the headless-specific tells (see Honest limits), and real-GPU WebGL (--gpu) is opt-in. But real, consistent fingerprints pass the consistency tier that synthetic ones fail *by construction* — and that tier is what stands between you and a login wall.

Multi-session in 10 lines

vb session new work

vb --session work start vb --session work go https://github.com # log in by hand once vb session new banking vb --session banking start vb --session banking go https://bank.example.com vb --session work click @e3 & # truly parallel — vb --session banking fill @e5 hi & # separate Chromes, no cookie bleed wait vb session list

Active-session resolution: --session FLAG → $VIBATCHIUM_SESSION env → ~/.config/vibatchium/active-session → default. Cap via VIBATCHIUM_MAX_SESSIONS=8 (default 8).

Multi-agent: shared sessions vs a private daemon

On one s

只显示了开头部分；其余内容请在仓库中阅读

vibatchium

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“网页与浏览器”中的其他服务器比较i

常见问题

替代选择

Browser Use

Chrome DevTools MCP

MCP Server Browser

作者的 README

vibatchium

Is this for you?

How it compares

What only vibatchium does

Install

(or pick extras: [fetch], [secrets], [llm], [rest])

Install as a skill / plugin

Quick start

Real Chrome vs fake Chrome

Multi-session in 10 lines

Multi-agent: shared sessions vs a private daemon