What it does
Verification browser for coding agents: headless WebKit, DOM eval, screenshots, pixel-diff.
- Connects 在你的电脑上运行
- Account or key No key needed
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 25/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 32/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
双击文件,然后在电脑版 Claude 应用中点击 Install
试一试
用 Hwatu 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Hwatu,或回答中出现 Hwatu 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Hwatu
Hwatu 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
你可以改用这些方式
A · 使用能连接 Hwatu 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
B · 开发者工具 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Claude Code 暂时无法连接 Hwatu
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 Hwatu 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
Cursor 暂时无法连接 Hwatu
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 Hwatu 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
VS Code 暂时无法连接 Hwatu
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 Hwatu 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 hongnoul 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于32天前
- ✓ 通过
有许可证
使用 MIT
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/hongnoul-hwatu)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6103 个服务器的 97%
- 发布到注册中心的时间比此分类中其他 6103 个服务器的 22% 更新
- 基础检查结果等于或优于此分类中其他 6103 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Hwatu 安全吗?
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于32天前,最新版本(0.6.0)于4个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 Hwatu | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
hwatu
Headless UI verification for coding agents
hwatu is a headless verification harness for coding agents: a warm WebKit daemon driven over CLI, MCP, or one JSON line per Unix-socket connection. Instead of "looks right to me", the agent gets one-call verified page checks in ~35 ms, pixel-diff scores it can climb, animations as numbers, and headless windows that never steal focus, at any parallelism. Jcode drives it natively as its browser backend. When a check needs a human (a CAPTCHA, a judgment call), hwatu focus materializes the same live session as a real window.
Documents
- Agent guide: protocol, primitives, verification loops
- Benchmarks: every number, measured, with methodology
- Vision: durable product principles, native platform strategy
- Human guide: hwatu as a tiling-WM browser, keybinds, hand-off
- Roadmap: portfolio priorities and product boundaries
- AI verification
- Tiling-WM browser
- Shared platform
- macOS research: measured WKWebView probes, competitor scan, and why macOS is verification-only
- Continuous improvement: activation metric, feedback loop, weekly cadence
- Launch kit: reusable copy, channels, and measurement plan
Install
curl -fsSL https://raw.githubusercontent.com/hongnoul/hwatu/main/scripts/install.sh | bash
One static binary plus your distro's webkitgtk-6.0 (the installer checks). On Arch: yay -S hwatu. From source: cargo build --release.
Then connect an agent:
hwatu setup # detect Claude Code, Cursor, Jcode, or MCP
Verification, not vibes
- "Pixel-perfect" is a claim. `match_percent: 97.49` is a measurement.
- One tool call per page check, ~35 ms. The same pass through warm-server Playwright is 5 calls and ~9x slower.
- Headless by default. No window pops, no focus stolen, you keep typing.
- One static binary + your distro's webkitgtk. No Node, no 170 MB Chromium download.
hwatu setup detects supported coding agents without changing their config. Choose a client explicitly:
hwatu doctor
hwatu setup --client claude --scope project --dry-run hwatu setup --client claude --scope project hwatu demo
Setup is previewable (--dry-run), idempotent, and reversible (--undo). Manual MCP configuration is one portable entry:
{ "mcpServers": { "hwatu": { "command": "hwatu", "args": ["mcp"] } } }
Or skip MCP: every command is a short CLI call or one newline-delimited JSON line over a Unix socket.
Connecting hwatu makes its tools available; a project instruction tells the agent when to use them. Add this to AGENTS.md, CLAUDE.md, or Cursor rules:
## Frontend verification
Use Hwatu after frontend changes. Exercise the affected user journey and verify its intended visible, navigational, or persisted result with expect. A successful click or clean console is not proof of success. Check console for additional JavaScript and request failures after verifying the outcome.
Then make the task's proof concrete:
Implement display-name editing on /settings. Use Hwatu to enter “Test User,”
save it, verify the visible success state, reload, confirm persistence, and report any console errors.
The verification loop:
hwatu --headless localhost:3000 # its window; you never see it
hwatu --headless staging.example.com # the reference
hwatu diff --id 2 --other 1 --heatmap /tmp/heat.png
{"match_percent":85.13,"regions":[{"x":0,"y":160,"w":2048,...}]}
hwatu motion --id 1 # the reference's animations, as numbers
easing cubic-bezier(0.25,1,0.5,1), 300ms, marquee 29.78px/s ...
...agent edits code...
hwatu diff --id 2 --other 1
{"match_percent":97.49} # climbing beats guessing
This loop took a clone of stripe.com's landing page from 85.1% to 98.8% pixel match. Reproduce it: scripts/demo/. A second real-agent scenario (four responsive viewport diffs, then live human hand-off) with evidence manifests: scripts/demo-aiuc/.
A full verification pass (open, load, eval, screenshot, close) is one command, one tool call, ~35 ms median (benchmarks):
hwatu check localhost:5173 --eval 'document.title' --shot=/tmp/after.png
{"title":"My App","eval":"My App","shot":"/tmp/after.png",
"console":[...],"load_ms":13,"total_ms":35}
For a repeatable repo-level contract that also owns the preflight, local dev server, responsive screenshots, source-staleness check, and evidence report:
hwatu verify .hwatu/about.verify.json
The same executor is exposed to MCP clients as verify_ui, so agent harnesses do not rebuild the orchestration loop. See the agent guide.
Generated HTML in hand and no server? hwatu render is the same one-call pass with the markup as input: no temp file, no python3 -m http.server:
echo '<h1>generated</h1>' | hwatu render --stdin --shot=/tmp/gen.png
{"rendered":true,"shot":"/tmp/gen.png","load_ms":5,"total_ms":28}
React to load, console, download, and window events without polling.
hwatu watch --kinds load,console
{"event":"load","seq":1,"window_id":7,"data":{"state":"started",...}}
MCP clients call subscribe_events for the same stream as notifications/hwatu/event. Full protocol and verification loops: agent guide.
Elsewhere, headless is decided at launch and a human can never see the session. In hwatu it is a window property, switchable live, in both directions: hwatu focus promotes any headless session to a real window for the human, state intact.
challenge is detection and hand-off only, by design: no solver APIs, no token injection, no fingerprint games.
The hand-off destination
The hand-off works because hwatu is also a real browser, built for tiling WMs. hwatu opens a window like your terminal opens a shell (your WM is the tab bar, there is none in the window): mainstream keybinds (ctrl+l, ctrl+f, ctrl+k palette, rebindable), native ad blocking (~119k EasyList rules compiled into WebKit's content-extension engine, zero JS in the request path), Chromium-curve scrolling, and unified shortform controls. Every window shares the one warm daemon (~56 MB per extra window), suspends when unfocused, and crash-restores at its last URL. Honest gaps: no Widevine or passkeys in WebKitGTK. WM configs (hyprland, sway, niri), keybinds, and setup: docs/human.md.
Features
- Headless / background / focused as a *per-window* property, switchable live
- Human hand-off:
hwatu focusdrops the live session into your tiling WM - Pixel-diff scoring: match percent + diff regions + heatmap (
diff) - Animations as numbers: duration, easing, velocity (
motion) - Deterministic animation frames: pin all animations at time t (
seek) - Page state as JSON, tokens not pixels (
snapshot) - Real input events with structured errors (
click/type/scroll/upload) - JS errors, console output, failed requests (
console) - Push event subscriptions as JSON lines or MCP notifications (
watch) - One-call page assertions with polling (
expect) - CAPTCHA / anti-bot detection with structured wait/resume (
challenge) - MCP server, plain CLI, and a 1-line JSON socket protocol
- A real browser as the hand-off destination: keybinds, media, ad blocking, crash restore
Why not Playwright or chrome-devtools-mcp?
Three ways to give an agent a browser:
| How it runs | What it costs the agent loop | |
|---|---|---|
| Cold library (Playwright, launched per task) | engine starts when the script does | fast to *call*, slow to *run*: every check pays engine startup; no state survives between tasks |
| Warm browser (your Chrome + devtools-mcp) | a full human browser stays resident | resources spent on tabs, extensions, sync, UI you never render, and its windows steal *your* focus while you work |
| hwatu | "the coldest warm daemon": engine hot, everything else absent | 8 ms spawns, 35 ms verified checks, invisible until *you* ask to see it (focus), interruptible in both directions |
hwatu keeps exactly what makes checks instant (engine, GPU context, compiled adblock, a prewarmed WebView) and nothing that serves a human *unless that human asked for a window*. That is why it idles warm without a tab bar, and why a kept-warm Playwright server driven the same way costs 341 ms per client to hwatu's 39 (benchmarks).
The second difference is what comes back. Playwright and chrome-devtools-mcp are automation APIs: they let an agent *drive* a browser, then hand back raw screenshots and DOM to eyeball. hwatu is a *verification* browser: the measurement primitives (check, diff, motion, expect) are built in, a window costs 13 ms, and headless is a window property, not a launch mode.
How hwatu compares
Legend: ✅ Yes / built-in · 🟡 Partial / limited · ❌ No
| Capability | Playwright | chrome-devtools-mcp | hwatu |
|---|---|---|---|
| Verify pass (load + eval + screenshot), warm in-process | 82 ms | n/a | 35 ms |
| Verify pass as a warm *service* (fresh client per check) | 341 ms | n/a | 39 ms |
| Tool calls per verify pass | 5 | 5 | 1 |
| Pixel-diff score + regions + heatmap | 🟡 1 | ❌ | ✅ |
| Animations as numbers, pinned mid-flight | ❌ 2 | 🟡 3 | ✅ |
| Headless ↔ headed on a *live* session | ❌ | ❌ | ✅ |
| Human hand-off mid-session, state intact | ❌ | ❌ | ✅ |
| No focus stealing at N parallel agents | 🟡 4 | 🟡 4 | ✅ |
| CAPTCHA detection + structured wait/resume | ❌ | ❌ | ✅ |
| No Node, no per-version browser download | ❌ | ❌ | ✅ |
1 toHaveScreenshot compares against stored goldens: pass/fail for test suites, not a score an agent can climb.
2 Standard practice is to disable animations or fast-forward to the end state to avoid flakes.
3 Raw CDP can query animation state, but there is no numeric summary of easing/velocity/keyframes.
4 Fine headless; every headed window pops and takes focus.
Comparison reflects each project at the time of writing;
corrections are welcome. Honest caveats: Playwright still wins
cold start (190 vs 435 ms, paid once per boot) and memory; hwatu
renders WebKit not Chromium (keep a Playwright matrix in CI for
engine-specific bugs), and it is Linux-only today. Full
head-to-head data and methodology:
[docs/benchmarks.md](docs/benchmarks.md