Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Hands-Rust MCP/CLI that sees the Windows desktop and clicks real Chrome

Details

External ID
49405405
Source
HN
Company
—
Product
—
Website domain
—
Launched
Aug. 23, 2026
Cohort
—
Upvotes
5
Upvotes percentile
0.12634408602150538
Tags
—
Fetched at
Sept. 10, 2026, 5:32 a.m.
Updated at
Sept. 10, 2026, 5:32 a.m.

Description

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.

Enrichment

Theme
markdown editors and writing tools
Vertical
Horizontal
Function
Agent / copilot
Audience
Developer
AI stance
AI-native
Project type
Commercial product
Normalized one-liner
desktop automation agent for windows
Manually corrected
False

Could you build this?

Partial While an MCP server wrapper is straightforward, reliable cross-window OS-level screen capture and low-level mouse/keyboard interaction on Windows require low-level OS automation hooks.

What it would actually take: The architecture requires an MCP protocol server in Rust interacting with Windows Win32 APIs (SendInput, Desktop Duplication API, or Graphics.Capture). The hard part is managing DPI scaling, elevated permissions, anti-cheat/antivirus interference, and accurate multi-monitor coordinate translation without UI test harnesses. It requires systems programming expertise in Windows desktop APIs and OS security boundaries.

Discussion

2 comments analyzed.

Feature requests: recording or visual walkthrough

Competitors

Other products that read as similar to this one — 76 launches clear the similarity bar, closest 8 shown.

Attention rank: #64 of 77 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 279 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a agent / copilot tool for Agriculture yet.