computer-use

Inspect and control visible local app windows through the Orca CLI.

1|Updated May 3, 2021
One-click install
npx skills add https://github.com/leogurja/dotfiles --skill computer-use-leogurja
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: computer-use
Source: https://github.com/leogurja/dotfiles/tree/main/home/dot_agents/skills/computer-use
Command: npx skills add https://github.com/leogurja/dotfiles --skill computer-use-leogurja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automating native desktop applications, external browser windows, and app webviews requires OS-level window inspection and input that page-only tools like Playwright or CDP cannot reach, and picking the wrong Orca executable can silently target the wrong build or even launch the GNOME screen reader. ## Core Features & Use Cases - Executable Resolution: Selects the correct Orca CLI per session using ORCA_CLI_COMMAND, ORCA_DEV_REPO_ROOT, orca-ide, or orca, avoiding the GNOME Orca screen reader conflict on Linux. - Version-Matched Guide Loading: Fetches the computer-use guide matching the running Orca build via ORCA skills get computer-use before executing any commands. - OS-Level Window Automation: Drives inspection and input in native apps, Chrome, Edge, Safari windows, and app webviews through orca computer. - Use Case: An agent needs to click through a native desktop app's dialog on Linux; it resolves orca-ide, loads the version-matched guide, and issues window-level input commands without touching the screen reader. ## Quick Start Ask the agent to load the computer-use guide with the resolved Orca executable and then inspect or interact with a visible application window.

Frequently Asked Questions about computer-use

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

FAQPage Schema
How do I automate native desktop app windows with Orca?▼

Resolve the correct Orca executable for your session, then run `ORCA skills get computer-use` to load the version-matched guide. The guide documents `orca computer` commands for window-level inspection and input in native apps and webviews.

When should I use computer-use instead of Playwright or CDP?▼

Use computer-use for OS and window-level control of native apps, external browser windows, and app webviews. Use Playwright or CDP for page-only browser automation, and orca-cli for Orca's embedded browser.

Which Orca executable should I run on Linux?▼

Use ORCA_CLI_COMMAND if set, orca-dev in a dev checkout with ORCA_DEV_REPO_ROOT, or orca-ide outside Orca-managed terminals. Never run bare `orca` on Linux, since it usually resolves to the GNOME Orca screen reader and starts speech.

What if the Orca CLI reports that Orca is not running?▼

Start Orca with `ORCA open --json` and retry the command. If the selected executable cannot run at all, report its exact error and stop rather than falling through to another executable that could target a different build.

What happens if the skills get command is unknown?▼

An unknown `skills get` command means the Orca build predates the guide feature. Updating Orca restores the guide; until then, use `--help` for read-only discovery and do not guess unsupported commands.