Handox is the cross-platform effector layer for AI agents — the ability to click, type, swipe, and read the screen across every device, through one binary and one API.
the motor cortex for the agentic era — LLMs think, Handox does
LLMs reason, plan, and decide — but when it's time to actually operate a computer or a phone, they hit a wall. Device control is fragmented: ADB for Android, AppleScript for Mac, Win32 for Windows, Playwright for browsers. None of them talk to each other, and every agent developer reinvents it, poorly, one platform at a time.
Five different tools, five mental models, five brittle integrations — each cloud-dependent, model-specific, or locked to one environment.
One installable binary. One opinionated API. Every platform behaves identically — if a capability is on the trait, every driver supports it or says exactly why not.
A single DeviceDriver trait — Windows, macOS, Android, iOS, browser, Linux. Cross-platform parity is the whole point.
Runs on your machine, not someone's cloud. No model lock-in, no per-action fees, no data leaving the device.
A default-deny permission engine gates every action; an append-only audit log records every click, keystroke, and tool call.
Drive a device on another machine across NAT and the internet through an end-to-end-encrypted relay. No inbound ports.
Speaks the Model Context Protocol out of the box — drop it into Claude, Cowork, or Claude Code and the tools just appear.
Native OCR (Vision / WinRT / Tesseract), fuzzy element matching, screenshot annotation, visual diff, and action record/replay.
Point your agent at Handox over MCP, REST, or the CLI. Every call flows through one router — permission-checked, audited, dispatched to the right driver.
Build the handox binary and drop it at a stable path. No agents, no daemons to babysit.
Add it as an MCP server, start the REST API + dashboard, or call it one-shot from the CLI.
Screenshot, click, type, swipe, launch apps, read the UI tree — on the host, a phone, a browser, or a device across the world.
// Wire Handox into any MCP client — the tools appear instantly. { "mcpServers": { "handox": { "command": "handox", "args": ["mcp"] } } } # …or start the REST API + fleet dashboard: $ handox start # → http://127.0.0.1:7600/ $ handox screenshot -o shot.png # one-shot from the CLI
Handox organises everything an agent can touch into five effector categories — the colour system that runs through the CLI, the dashboard, and the mark itself.
Local filesystem
Browser & HTTP
OS & process
Third-party APIs
Database & storage
Open-source under Apache-2.0. Clone it, build it, and start driving.