JSON output contract

August 13, 2026 ยท View on GitHub

Every command returns structured JSON:

{
  "version": "2.3",
  "ok": true,
  "command": "click",
  "data": { "action": "click" }
}

Errors include machine-readable codes and recovery hints:

{
  "version": "2.3",
  "ok": false,
  "command": "click",
  "error": {
    "code": "STALE_REF",
    "message": "Element at @e7 no longer matches the last snapshot",
    "suggestion": "Run 'snapshot' to refresh refs, then retry",
    "recovery": {
      "strategy": "refresh_snapshot_then_retry_original",
      "retryable": true,
      "requires_fresh_snapshot": true
    },
    "disposition": {
      "delivery": "not_delivered",
      "retry": "safe"
    }
  }
}

Version 2.1 replaces the 2.0 error.retry_command string with the structured error.recovery object and adds error.disposition. Consumers must select a recovery strategy from recovery.strategy only when disposition.retry is safe; command strings from older envelopes must not be executed blindly. The removed retry_command field has no compatibility alias.

Error codes

CodeMeaning
PERM_DENIEDAccessibility permission not granted
ELEMENT_NOT_FOUNDNo element matched the ref or query
APP_NOT_FOUNDApplication not running or no windows
STALE_REFRef could not be re-identified in the live UI
AMBIGUOUS_TARGETRef recovery matched multiple plausible targets
SNAPSHOT_NOT_FOUNDSnapshot ID is missing or expired
POLICY_DENIEDPhysical/headed path blocked by policy
ACTION_FAILEDThe OS rejected the action
ACTION_NOT_SUPPORTEDThe target does not expose the requested action
APP_UNRESPONSIVEThe matching application stopped responding
PLATFORM_NOT_SUPPORTEDAdapter method not implemented on this platform
TIMEOUTWait condition expired
INVALID_ARGSInvalid argument values

Exit codes

0 success, 1 structured error (JSON on stdout), 2 argument parse error.