computer-use
Utilisez l'interface en ligne de commande computer-use d'Orca pour inspecter et manipuler les fenêtres d'applications de bureau locales via des arbres d'accessibilité, des captures d'écran et des actions UI sécurisées. Utilisez pour l'interaction avec les applications de bureau : lister les applications/fenêtres, obtenir l'état de l'application, lire l'UI visible, cliquer sur des contrôles, taper, appuyer sur des touches, faire défiler, glisser, définir des valeurs ou effectuer des actions d'accessibilité. Utilisez également pour les fenêtres de navigateur, les vues web, l'UI de l'application Orca ou toute autre UI de bureau. Les déclencheurs incluent "computer use", "orca computer", "read Spotify", "read Slack", "control/click/read in a...
npx skills add https://github.com/stablyai/orca --skill computer-useComputer Use
This discovery stub loads the version-matched guide from the Orca executable used for this session.
Resolve the CLI for this session
Choose the executable once and reuse it for every later command:
- If the
ORCA_CLI_COMMANDenvironment variable is set, use its value. Orca exports this for managed WSL sessions. - Otherwise, in a dev checkout whose session exposes
ORCA_DEV_REPO_ROOT, useorca-dev. - Otherwise, on Linux outside an Orca-managed terminal, use
orca-ide. Never run bareorcathere — outside Orca's terminals it normally resolves to the GNOME Orca screen reader (/usr/bin/orca) and starts speech on the user's machine. - Otherwise, use
orca.
Below, ORCA is a placeholder for the executable you resolved. Substitute it before
running anything; do not create a shell variable or run ORCA literally. This works the
same way in POSIX shells, PowerShell, and cmd.exe.
If the selected executable cannot run, report its exact error and stop. Do not fall through to another executable, which could silently target a different Orca build.
Load the version-matched guide before running Orca commands
ORCA skills get computer-use
Prefer --json. Use the selected executable's --help for commands or flags the guide does
not cover. If a command reports that Orca is not running, start it with ORCA open --json
and retry. If it fails with runtime_access_denied, your sandbox blocked the connection:
re-run it with escalated permissions, and do not run ORCA open or restart Orca. If
skills get is unknown, explain that updating Orca restores the guide; use --help for
read-only discovery and do not guess unsupported commands.