Show HN:Hands——能看见 Windows 桌面并点击真实 Chrome 的 Rust MCP/CLI
Hands 让编码 Agent 像用户一样操作 Windows PC 和日常 Chrome 配置:观察屏幕、移动真实鼠标、输入、点击,而不把 Chrome 变成自动化浏览器。它是 Rust 编写的 MCP/CLI;Grok、Codex、Claude Code、OpenCode 等 Harness 可调用 observe、click、type、scroll。observe 返回截图路径和少量元素列表(UIA 与可选 Chrome DOM id),点击通过 OS SendInput 沿贝塞尔路径完成,不是 DevTools 点击。它不使用 Playwright、Puppeteer 或远程调试端口,Chrome 无需额外启动参数;但注入输入仍可能被识别。
查看英文原文
Show HN: Hands-Rust MCP/CLI that sees the Windows desktop and clicks real Chrome
I built Hands because I wanted a coding agent to use this Windows PC and a real Chrome profile the way I do: look at the screen, move the real mouse, type, click , without turning Chrome into an automation browser. It is a Rust MCP/CLI. A harness (Grok, Codex, Claude Code, OpenCode, etc.) calls tools like observe, click, type, scroll. Observe is a screenshot path plus a small element list (UIA + optional Chrome DOM ids). Click is OS SendInput on a Bézier path, not a Chrome DevTools click. There is no Playwright, no Puppeteer, no remote debugging port. Daily Chrome is launched with no extra flags, or attached if it’s already open. Sites that key on CDP/automation flags mostly don’t see that. They can still see injected input (LLMHF_INJECTED). A tiny unpacked Chrome extension can fuse page structure (chr: ids, listing cards) so the model isn’t guessing from pixels. Sideload is manual. Fusion dies if the service worker goes inactive; reload the card. What it is good for: personal research on your own desk. “Find a Camry on cars.com,” read a page, fill a ZIP, dismiss a cookie banner. What it is not: • Not a sandbox. It can click whatever is on screen, including checkout and Easy Apply. • Confirm-before-money is best-effort classification in the binary, not a guarantee. Prompt injection from the screenshot/DOM is real; the binary treats that text as untrusted, the model might not. • Not a CAPTCHA solver on daily Chrome. Two visible tries, then it yields and waits for the puzzle to go away. • Windows only. • Install is: build the exe, register a native-messaging host, sideload the extension, point an MCP client at hands mcp. README is the runbook. Missing an API key does not fail the build; do_task is optional. • Logs live under %LOCALAPPDATA%\hands\logs\. The extension asks for <all_urls> so it can map the tab you’re looking at. Repo: https://github.com/Ryan-AI-Studios/hands (MIT) Happy to answer how observe/fusion/the fence work. If you try it, Pause/Break is the kill switch.
Show HN: Hands-Rust MCP/CLI that sees the Windows desktop and clicks real Chrome
I built Hands because I wanted a coding agent to use this Windows PC and a real Chrome profile the way I do: look at the screen, move the real mouse, type, click , without turning Chrome into an automation browser.<p>It is a Rust MCP/CLI. A harness (Grok, Codex, Claude Code, OpenCode, etc.) calls tools like observe, click, type, scroll. Observe is a screenshot path plus a small element list (UIA + optional Chrome DOM ids). Click is OS SendInput on a Bézier path, not a Chrome DevTools click.<p>There is no Playwright, no Puppeteer, no remote debugging port. Daily Chrome is launched with no extra flags, or attached if it’s already open. Sites that key on CDP/automation flags mostly don’t see that. They can still see injected input (LLMHF_INJECTED).<p>A tiny unpacked Chrome extension can fuse page structure (chr: ids, listing cards) so the model isn’t guessing from pixels. Sideload is manual. Fusion dies if the service worker goes inactive; reload the card.<p>What it is good for: personal research on your own desk. “Find a Camry on cars.com,” read a page, fill a ZIP, dismiss a cookie banner.<p>What it is not: • Not a sandbox. It can click whatever is on screen, including checkout and Easy Apply. • Confirm-before-money is best-effort classification in the binary, not a guarantee. Prompt injection from the screenshot/DOM is real; the binary treats that text as untrusted, the model might not. • Not a CAPTCHA solver on daily Chrome. Two visible tries, then it yields and waits for the puzzle to go away. • Windows only. • Install is: build the exe, register a native-messaging host, sideload the extension, point an MCP client at hands mcp. README is the runbook. Missing an API key does not fail the build; do_task is optional. • Logs live under %LOCALAPPDATA%\hands\logs\. The extension asks for <all_urls> so it can map the tab you’re looking at.<p>Repo: <a href="https://github.com/Ryan-AI-Studios/hands" rel="nofollow">https://github.com/Ryan-AI-Studios/hands</a> (MIT)<p>Happy to answer how observe/fusion/the fence work. If you try it, Pause/Break is the kill switch.
- 来源
- Show HN · show-hn
- 证据角色
- project_and_comment_discovery
- 时间状态
- known
- 用户判决
- 未判