02 · Show
Peeve highlights the answer, then clicks it.
The user asks. The cursor moves through your real interface at human speed, narrating, while they watch.
Install Peeve ↗01
The user asks
In their own words, from inside your product. No keyword matching, no menu of canned intents.
02
Peeve finds the element
By reading the live accessibility tree and scoring candidates against a stored fingerprint.
03
It moves, pauses, clicks
600–900 px per second, then a 200ms highlight ring before every click.
01How does Peeve know where a button is?
Peeve stores each element by role, accessible name, landmark position and neighbours, never by CSS class or XPath. At runtime it reads the live accessibility tree and scores candidates against that fingerprint. Above 0.85 it acts. Between 0.60 and 0.85 it checks a screenshot first. Below 0.60 it stops and says so.
02What happens when your interface changes?
Nothing breaks silently. Confidence drops, the route is flagged, and Peeve re-captures it on the next session that visits. A renamed button merges automatically. A restructured page waits for a 30-second confirmation in your dashboard.
03Can the user take over?
Any mouse or keyboard input pauses Peeve within 100 milliseconds. The cursor greys, the trail freezes, and a Paused pill appears. It never resumes without being asked.
04Why does the cursor move slowly?
So the user learns the path. Peeve travels at 600–900 pixels per second and pauses 200 milliseconds with a highlight ring before every click. The pause is also a safety mechanism: it's the window in which a user can stop an action they didn't want.
What Show doesn't do
Cross-origin iframes
Canvas-only interfaces
Native mobile apps
Anything outside the routes you allow
The confidence ladder
Peeve only acts when it's sure. And it tells you when it isn't.
≥ 0.85
Acts
Peeve moves the cursor and clicks: a high-confidence match against the live accessibility tree.
0.60 – 0.85
Checks first
Peeve verifies against a screenshot before it acts, so an ambiguous match never becomes a wrong click.
below 0.60
Stops and says so
Peeve hands off rather than guessing, and that session isn't billed, because we don't charge for failure.
Why teams choose Peeve
Users learn the path
The cursor moves at human speed and pauses before it acts, so people remember where a control lives instead of asking again.
Never a wrong answer
Elements are found by semantic fingerprint against the live tree; below 0.60 confidence Peeve stops rather than guessing.
Nothing to author
Guidance is generated live from the current interface. No tours to build or re-record when the UI changes.
14-day trial, no cardInstalls in an afternoonRead-only until you widen itKill switch in one commandCancel anytime, no lock-in