Skip to main content
Visor lets AI agents operate running mobile apps, remember what they learn, and verify the result against the live UI.
2.9x faster in one internal four-flow comparison with live Appium MCP navigation. Across four mobile flows, Visor’s map-driven execution finished in 249 seconds versus 723 seconds for the Appium MCP baseline: a 2.9x speedup and 66% less execution time. The deepest flow was 5.7x faster, and Visor used 31% fewer execution tokens overall.
The comparison reached the same answers and the same app-state block in both approaches. All four Visor route plans replayed on the first try without route rediscovery. The shallow, one-tap flow was effectively tied; the largest gains appeared as navigation depth increased. This was one app and one fixed task set, not a general performance guarantee; results will vary with the app, device, route depth, and existing map state. It does six things:
  1. Connects to a running iOS or Android app.
  2. Builds compact semantic memory for screens, safe actions, and known routes.
  3. Executes deterministic preferred and recovery paths in one request.
  4. Performs real UI actions and captures targeted evidence from the live app.
  5. Evaluates assertions against observed UI state.
  6. Persists reports and artifacts so a person or an LLM can review what happened.

​
What Visor is for

Visor is built for cases where code alone is not enough to verify behavior. Typical agent-driven use cases:
  • Discover a new app once, then reuse the resulting semantic map across tasks.
  • Navigate known flows without repeatedly inspecting screenshots or UI source.
  • Recover from unknown screens with exact observation tokens and safe alternate paths.
  • Verify that a UI change actually rendered on screen.
  • Compare before and after state using screenshots and UI source.
  • Run the same scenario repeatedly to measure stability.
  • Produce machine-readable evidence for review, debugging, or automation.

​
Product scope

Visor currently supports mobile applications only. Supported scope today:
  • Android apps through Appium and UiAutomator2.
  • iOS apps through Appium and XCUITest.
  • Real device or simulator interaction.
Out of scope today:
  • Web applications.
  • Desktop applications.
  • Rich assertion types beyond visibility checks.

​
Core building blocks

The product is organized around a small set of concepts.

​
Documentation map

Read the pages in this order if you are new to Visor: Use the reference section when you need exact field names, inputs, outputs, or error behavior:

​
What Visor returns

Every operation returns a structured response envelope. The envelope always tells you:
  • whether the operation succeeded or failed
  • when it started and ended
  • which artifacts were produced
  • what the next logical action is
  • which structured payload belongs to the operation
Longer flows such as scenario runs also write files to disk so the run can be audited after the fact.