Requirements

Before using AgentKVM, ensure the following are installed and available:

• - AgentKVM CLI — INLINECODE0
• Node.js >= 18
• ffmpeg — required for screenshot capture (brew install ffmpeg on macOS, apt install ffmpeg on Linux)
• NanoKVM-USB hardware connected to the host machine via USB
• HDMI input from the target device connected to the NanoKVM-USB

Run agentkvm status to verify everything is set up correctly. If the CLI is not found, install it first. If the device is not detected, check agentkvm list for available serial ports.

AgentKVM — AI-Driven Device Control

AgentKVM lets you see and operate physical devices (iPhones, Android phones, PCs, Macs, Linux machines) connected via NanoKVM-USB hardware. You take screenshots to observe the screen, then send mouse clicks, keyboard input, and scrolls to interact — just like a human sitting in front of the device.

Core Loop

Every interaction with a physical device follows the same pattern:

CODEBLOCK0

1. 1. Screenshot — capture what's currently on screen
2. Analyze — look at the image to understand the UI state
3. Act — click, type, scroll, or drag based on what you see
4. Verify — take another screenshot to confirm the action worked

This loop is your fundamental building block. Chain multiple iterations to accomplish complex tasks.

Quick Start

Check connection

CODEBLOCK1

If this fails, the device isn't connected. Check the serial port with agentkvm list.

See the screen

CODEBLOCK2

Returns { "path": "/path/to/screenshot.png", ... }. Read the image to see what's on screen.

Interact

CODEBLOCK3

Remote operation

If AgentKVM is running on another machine, all commands work identically with --remote:

CODEBLOCK4

Or use the HTTP API directly — see references/api.md.

How Coordinates Work

This is critical to get right. When you analyze a screenshot and identify a UI element at pixel (x, y), those coordinates are relative to the screenshot image itself — top-left is (0, 0). Pass these coordinates directly to agentkvm mouse click x y.

AgentKVM handles the translation to the actual hardware coordinates internally, based on the device type and crop settings. You don't need to do any math.

Two coordinate modes

The device type determines how coordinates are translated:

"device" mode (iPhone, Android) — The cropped region IS the device's full screen. HID absolute coordinates 0–4096 map to the device's own display. Use this when the HDMI output shows the device screen within a larger capture frame.

"frame" mode (PC, Mac, Linux) — The cropped region is just a visual focus area; HID coordinates still map to the full monitor. Use this when you're controlling a computer where the capture resolution matches the target display.

The mode is selected automatically from the config. You rarely need to think about it.

Implementing a Task

When asked to perform a GUI task (e.g., "open Safari and search for X"):

Step 1: Observe first

Always start with a screenshot. Never assume what's on screen.

CODEBLOCK5

Read the returned image file. Describe what you see — this grounds your actions in reality.

Step 2: Plan your actions

Break the task into individual interactions. For "open Safari and search for X":

1. 1. Find the Safari icon → click it
2. Wait for Safari to load → screenshot to verify
3. Find the address bar → click it
4. Type the search query
5. Press Enter
6. Screenshot to verify results

Step 3: Execute with verification

After each significant action, take a screenshot to verify it worked. Screens can be slow to update, so add brief waits between actions when needed (use sleep in your script).

Common pattern in a bash script:

CODEBLOCK6

Step 4: Handle failures

If an action didn't produce the expected result:

• - The element might have moved — take a fresh screenshot and re-locate it
• The screen might not have updated yet — wait and retry
• You might have clicked the wrong spot — re-analyze and adjust coordinates

Config Reference

All settings live in ~/.config/agentkvm/config.json. A typical setup:

CODEBLOCK7

Key fields:

• - serialPort — path to the NanoKVM-USB serial device
• INLINECODE15 — HDMI capture resolution
• INLINECODE16 — video capture device name or index
• INLINECODE17 — determines coordinate mode (iphone/android = device, pc/mac/linux = frame)
• INLINECODE23 — sub-region of the capture frame to use as the working area

When config is set, you can run bare commands without flags: agentkvm screenshot, agentkvm mouse click 100 200, etc.

Tips for Reliable Automation

Prefer clicking on text labels over icons — text is easier to locate precisely in screenshots.

Use --json for programmatic access — all commands support it and return structured data you can parse.

Double-click when single-click doesn't respond — some UI elements need --double.

Scroll in small increments — --delta 1 or --delta -1 is one scroll step. Use multiple steps with verification screenshots in between.

Type slowly for unreliable connections — increase --delay (default 50ms) if characters get dropped.

Use key combos for navigation — cmd+space (Spotlight), alt+tab (window switch), ctrl+c (cancel) are often faster than finding and clicking UI elements.

For the full CLI reference, key combo syntax, and HTTP API details, see references/api.md.