computer-use
We need to translate the given text from English to Vietnamese, preserving the name "computer-use" and other technical terms. The instruction says to translate only the text inside <text>, and not include the name unless it appears in the source text. The name "computer-use" appears in the source text as "computer-use CLI" and also in the triggers list as "computer use" (without hyphen). We should preserve the exact form as in source: "computer-use" when it appears with hyphen, and "computer use" when without. Also preserve "Orca", "CLI", "UI", "Spotify", "Slack", etc. No extra commentary. Let's translate paragraph by paragraph. First sentence: "Use Orca's computer-use CLI to inspect and operate local desktop app windows through accessibility trees, screenshots, and safe UI actions." -> "Sử dụng CLI computer-use của Orca để kiểm tra và vận hành các cửa sổ ứng dụng desktop cục bộ thông qua cây trợ năng,
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.