computer-use

Automate desktop GUI interactions via accessibility-tree element indexing across macOS, Windows, and Linux.

5|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/AjayRajan05/VoiceOS --skill computer-use-ajayrajan05
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: computer-use
Source: https://github.com/AjayRajan05/VoiceOS/tree/main/skills/bundled/community/computer-use
Command: npx skills add https://github.com/AjayRajan05/VoiceOS --skill computer-use-ajayrajan05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Driving a user's real desktop applications normally requires fragile pixel-coordinate automation that steals the cursor and keyboard focus. This Skill lets an AI agent click, type, scroll, and drag inside native apps in the background, using accessibility-tree element indices instead of raw coordinates, without interrupting the user's own work. ## Core Features & Use Cases - Element-index targeting: Capture a screenshot with numbered overlays on every interactable element (SOM mode), then click or type by element index rather than pixel coordinates, which works reliably with any tool-capable model. - Background operation: Actions never move the user's cursor, steal keyboard focus, raise windows, or switch virtual desktops, so the user can keep working in another window. - Cross-platform support: Works on macOS (AX), Windows (UIA), and Linux (AT-SPI) through the cua-driver layer, with platform-appropriate keyboard shortcuts and failure diagnostics. - Use Case: Ask the agent to fill out a form in a native desktop app like Mail or Figma while you continue typing in your editor; the agent captures the app, clicks fields by index, and verifies each step with follow-up screenshots. ## Quick Start Ask the agent to open a specific desktop application and perform a GUI task, such as "capture Chrome and click the Sign In button", and it will screenshot the app, index its elements, and act on them in the background.

Frequently Asked Questions about computer-use

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

FAQPage Schema
How do I automate clicking buttons in desktop apps with an AI agent?▼

Capture the target app with computer_use in SOM mode to get a screenshot with numbered overlays on every interactable element, then call click with the element index. Element indices are far more reliable than pixel coordinates across models.

What is the difference between computer_use and browser automation tools?▼

Browser tools drive a headless Chromium and are more reliable for web tasks. Use computer_use only when the task requires the user's actual native apps, such as Finder, Mail, Figma, or desktop chat clients.

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

Yes, it is cross-platform through cua-driver, using the accessibility framework of each host: AX on macOS, UIA on Windows, and AT-SPI on Linux. Keyboard shortcuts adapt per platform, such as cmd+s on macOS versus ctrl+s elsewhere.

Why did my click fail or hit the wrong element?▼

Element indices are only valid until the next capture, so a stale index causes an explicit error rather than a wrong click. Re-capture before clicking, and check whether a modal dialog is blocking input.

Can the agent type passwords or handle permission dialogs?▼

No. The skill hard-blocks typing passwords, API keys, or credit card numbers, and the agent must stop and ask the user before interacting with permission dialogs, payment UI, or 2FA challenges.

What should I do when computer_use captures return empty screens?▼

On Linux this usually means DISPLAY is unset or you are on pure Wayland; on Windows you may be in Session 0 instead of the interactive desktop. Run python main.py computer-use doctor for a structured diagnostic report.