Visor
Visor gives AI agents verified visibility into running mobile apps.
Instead of inferring UI behavior from code alone, Visor captures evidence from the live app: interactions, screenshots, UI source, assertions, and run artifacts.
What Visor does
- interacts with iOS and Android apps through Appium
- captures screenshots and UI source from live app state
- executes repeatable scenarios with ordered steps
- evaluates visibility assertions after execution
- writes artifacts and reports for review and automation
- measures determinism across repeated runs
Why teams use it
- reduce guesswork in agent-driven UI work
- verify real app behavior instead of code intent alone
- keep reproducible evidence for debugging and review
- add a repeatable verification layer around mobile UI changes
Scope
Visor is focused on mobile app verification.
Supported today:
- Android
- iOS
- real Appium-backed runs
- mock runs for predictable dry-run behavior
Documentation
Comprehensive product documentation lives in the docs site.
1 maintainer
Metadata
1 maintainer
Release files for visor-ai 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| visor_ai-0.1.1.tar.gz | 21.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| visor_ai-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.0 kB
Release files / visor_ai-0.1.1.tar.gz
| Download URL | visor_ai-0.1.1.tar.gz |
|---|---|
| Size | 21.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
efab68b0213f51890686da15cb769de3111ac4e2eaf4dac3d6978fbf39f5eb0a
|
|
BLAKE2b-256 checksum How to use checksums |
803a906ef631d93341aa2dedbe2bcb4aeff3c3d9ec3684032e127062ab4712a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 30, 2026.
Transparency logRelease files / visor_ai-0.1.1-py3-none-any.whl
| Download URL | visor_ai-0.1.1-py3-none-any.whl |
|---|---|
| Size | 21.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
200d8bdc9ae2ae579660fa6facd0eb96c20edf7b3899be4e3d7a59a7c27ccbeb
|
|
BLAKE2b-256 checksum How to use checksums |
27b16cf65e6c73e2984e6d4d29c73bd6e1f1ca1ec6081792ba5d2d363f29b96a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 30, 2026.
Transparency log
