Skip to main content
The yoqa CLI is plain commands in, structured output out — a natural tool for Cursor, Claude Code, Codex, and similar agents. Instead of clicking through the UI, your coding agent can inspect the screen, drive the device, and maintain cases as part of the normal loop: change code → ask it to test → get pass/fail with screenshots.

​
Install the CLI and skill

Both live in the desktop app Settings → CLI & Agents (or install the CLI from npm with npm i -g @yoqa/cli / npx @yoqa/cli):
  • Install CLI — links yoqa into ~/.local/bin (or use the npm global binary).
  • Install skill — installs yoqa-testing into common agent skill directories so the agent knows the workflows without you pasting docs.
Full command surface: CLI reference. Public index (once hosted): https://docs.yoqa.ai/llms.txt.

​
What you can do locally

No cloud sign-in for these Phase 1 workflows.

​
Debug loop: inspect → act → verify

  1. Connect — yoqa devices connect <device-id>.
  2. Ensure the app is on device — install a build or launch an already-installed app.
  3. Loop one step at a time:
    • Inspect — yoqa screen (prefer over screenshot / --full).
    • Act — one yoqa action …, preferably -d "…".
    • Verify — yoqa screen again (or yoqa screenshot for a visual check).
Never fire an action blind.

​
Reading the screen efficiently

​
Hand off to the Yoqa agent

Your coding agent authors and maintains cases; yoqa runs create (or the Runs UI) hands a saved case to the Yoqa agent, which runs the perception loop autonomously. That split keeps exploration cheap and regression hands-off.

CLI reference

Every command and option

How the agent thinks

Perception → decision → action