Hands for software with no API, governed.

API first. Where there is none, Qvrone reads the screen as named elements from the accessibility tree or the page. The gate confirms every proposed action before it runs and verifies the effect after.

Request access Read the docs

Fig.1 · sample

accessibility tree

window “Tally — Voucher”
form “Receipt”
textbox “Amount” e12
button “Save” e14
button “Delete” e15
status “Voucher saved”

model propose click(e14)

gate re-read tree · e14 = button “Save” in form “Receipt” ✓

gate policy: save_voucher → allow · receipt r-7c1 (one use)

hands click e14 · receipt spent

check re-read · status “Voucher saved” appeared → confirmed

How it works.

01 /
Read
The screen as named elements, not pixels.
02 /
Confirm
The gate re-reads the tree to confirm role, name and ancestry; a one-use receipt authorises the action.
03 /
Verify
A fresh read checks the effect.