computer-use

Automates desktop GUI interactions via screenshots, accessibility trees, and element-indexed clicks.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/decniner/HermesP1 --skill computer-use-decniner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: computer-use
Source: https://github.com/decniner/HermesP1/tree/main/.hermes-backup/skills/computer-use
Command: npx skills add https://github.com/decniner/HermesP1 --skill computer-use-decniner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cua-driver.

What problem does it solve? Automating native desktop applications normally requires moving the user's cursor and stealing keyboard focus, interrupting their work. This Skill drives macOS, Windows, and Linux desktops in the background using accessibility trees and numbered element overlays, so GUI automation runs without disturbing the user. ## Core Features & Use Cases - Background GUI Automation: Click, type, scroll, and drag in any app without moving the real cursor, raising windows, or switching virtual desktops. - Element-Indexed Targeting: Capture screenshots with numbered overlays and an accessibility-tree index, then click elements by index instead of fragile pixel coordinates. - Cross-Platform Support: Works on macOS (AX), Windows (UIA), and Linux (AT-SPI) with any tool-capable model, powered by cua-driver. - Use Case: Ask the agent to fill out a form in a native desktop app like Mail or Figma while you keep typing in your editor; it captures the app, clicks the right fields by index, and verifies each step. ## Quick Start Ask the agent to open a specific desktop application and perform a task in it, such as clicking a button or filling a field, using the computer_use tool.

Frequently Asked Questions about computer-use

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate desktop app clicks without moving the mouse?▼

Use the computer_use capture action with mode som to get a screenshot with numbered element overlays, then call click with the element index. Input is routed in the background, so the real cursor and keyboard focus are never affected.

How to click UI elements reliably with an AI agent?▼

Capture the target app first to get an accessibility-tree index, then click by element number rather than pixel coordinates. Re-capture before each click because element indices become stale after any new capture.

Does computer-use work on Windows, macOS, and Linux?▼

Yes, it supports all three platforms through cua-driver, using AX on macOS, UIA on Windows, and AT-SPI on Linux. Keyboard shortcuts differ per platform, such as cmd+s on macOS versus ctrl+s elsewhere.

When should I use computer_use instead of browser automation tools?▼

Use browser tools for web tasks since they run a headless Chromium more reliably. Reserve computer_use for native desktop apps like Finder, Mail, Figma, or games that browser tools cannot reach.

Why does computer_use return empty captures or stale element errors?▼

Empty captures usually mean DISPLAY is unset on Linux or the session is non-interactive on Windows. Stale element errors mean the index expired after a new capture; re-capture before clicking, or run hermes computer-use doctor for diagnostics.