computer-use

Automates desktop GUI interactions via background clicking, typing, and scrolling across macOS, Windows, and Linux.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill computer-use-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: computer-use
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/autonomous-ai-agents/computer-use
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill computer-use-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automating native desktop applications normally requires stealing the user's cursor and keyboard focus, interrupting their work. This Skill drives the desktop in the background — clicking, typing, scrolling, and dragging — without moving the real cursor, grabbing focus, or switching virtual desktops, and it works with any tool-capable model. ## Core Features & Use Cases - Element-indexed interaction: Capture screenshots with numbered overlays on every interactable element plus an accessibility-tree index, then click by element index instead of unreliable pixel coordinates. - Verify-and-escalate ladder: Every input action returns a structured verdict (confirmed, unverifiable, suspected_noop) with escalation recommendations from background element clicks to pixel coordinates, typed browser-page routes, and foreground delivery. - Cross-platform support: Works on macOS (AX), Windows (UIA), and Linux (AT-SPI) with platform-appropriate keyboard shortcuts and failure diagnostics via hermes computer-use doctor. - Use Case: Ask the agent to fill out a form in a native desktop app like Figma or Mail while you keep typing in your editor — the agent captures the app window, clicks fields by index, types values, and verifies each step without ever taking over your screen. ## Quick Start Ask the agent to use computer_use to capture the Chrome window and click the Sign In button by its element index.

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 user's cursor?▼

Use the computer_use capture action with mode="som" to get a screenshot with numbered element overlays, then call click with the element index. cua-driver delivers input in the background, so the real OS cursor never moves and keyboard focus is not stolen.

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

Headless browser tools run a separate Chromium instance and are more reliable for pure web tasks. Use computer_use when the task requires the user's actual native apps, such as Finder, Mail, Figma, native chat clients, or games.

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

Yes, it is cross-platform. It uses the host accessibility framework — AX on macOS, UIA on Windows, and AT-SPI on Linux — and adapts keyboard shortcuts per platform, such as cmd+s on macOS versus ctrl+s on Windows and Linux.

Why did my computer_use click have no effect?▼

Read the structured verdict returned by the action. An effect of "suspected_noop" or a structured refusal means climb the escalation ladder: retry by pixel coordinate, use the typed browser-page route when available, then re-issue with delivery_mode="foreground".

Can computer_use type passwords or click permission dialogs?▼

No. The Skill hard-blocks typing passwords, API keys, and credit card numbers, and it never clicks permission dialogs, payment UI, or 2FA prompts. Dangerous shell patterns in typed text are also blocked at the tool level.

When should I not use computer_use for a task?▼

Avoid it for web automation that headless browser tools can handle, for file edits where read_file or write_file applies, and for shell commands where the terminal tool is appropriate. Reserve it for native GUI application control.