# Autonom > Autonom lets an AI coding agent test and debug Android and iOS apps on an Android emulator or the iOS Simulator. The agent loads Autonom's skills and runs one command line that answers in JSON, with no MCP server: it reads the screen as a compact tree, acts on controls by what they say, reads logs and, with consent, network traffic, and brings back screenshots and a journal of every step as evidence. - Source: https://github.com/aiatsuk/autonom - License: MIT - Version: 0.36.1 - Changelog: https://github.com/aiatsuk/autonom/blob/main/CHANGELOG.md - Every page in one file: https://autonom.yatsuk.me/llms-full.txt ## Landing - [Autonom](https://autonom.yatsuk.me/index.md): Your agent tests and debugs your app on an iOS Simulator or an Android emulator, and brings back the evidence. ## Docs - [Overview](https://autonom.yatsuk.me/docs/index.md): Let your agent drive an iOS Simulator or an Android emulator, and bring back proof of what it saw. - [Install](https://autonom.yatsuk.me/docs/install/index.md): One script puts the `autonom` command line on your PATH and gives your agent its skills. Then `autonom doctor` says what works on this machine and how to fix the rest. - [Your first check](https://autonom.yatsuk.me/docs/first-check/index.md): Install Autonom, point your agent at a Simulator or emulator, and get back a screenshot and a journal of what it did. - [Sessions and targets](https://autonom.yatsuk.me/docs/sessions/index.md): Own one target, the emulator or Simulator your agent drives, and keep a journal of every verb it runs. A verb is one Autonom command, such as `ui tap`. - [Skills and routing](https://autonom.yatsuk.me/docs/skills/index.md): Your agent loads only the skills a task needs. It reads one map, routes to one stack, and adds device skills only when the running app must prove something. - [Read and drive the screen](https://autonom.yatsuk.me/docs/screen/index.md): Your agent reads the screen as a compact tree of controls and acts on a control by what it says. The same verbs work on an Android emulator and an iOS Simulator. - [Device state](https://autonom.yatsuk.me/docs/device-state/index.md): Put the app straight into the state you want to test: a deep link, a permission, a location or a file. Each verb answers in JSON, so your agent checks what happened instead of assuming it. - [Evidence](https://autonom.yatsuk.me/docs/evidence/index.md): Bring back proof, not a claim: screenshots that carry their own provenance, logs narrowed to your app and a report of every step. - [Network](https://autonom.yatsuk.me/docs/network/index.md): See what your app really sent, and make its server fail on purpose to check what the user sees. - [Report bundle](https://autonom.yatsuk.me/docs/report-bundle/index.md): Keep a run as one portable directory: its flow, its steps, its report and its evidence, each file recorded by its digest. Autonom never rewrites a finalized bundle, and replay, the agent report and `ci pack` verify it before they read it, which catches a damaged file or an edit that left the records alone. `ci merge` and `ci finalize` do not check the digests, so verify packs from other runners before you merge them. The digests are not a signature, so take bundles only from a source you trust. - [Agent report](https://autonom.yatsuk.me/docs/agent-report/index.md): Give your agent a run as compact JSON instead of an HTML report. The agent report names the failure, the steps and the evidence each one kept, and one step can be inspected on its own. - [Flows](https://autonom.yatsuk.me/docs/flows/index.md): Save a journey that worked once as a file your agent replays on every change. A mistake is refused with its line and column, and a failed run tells you how to fix the file. - [App memory](https://autonom.yatsuk.me/docs/memory/index.md): Your agent learns an app once and reuses what it learned. Notes stay on your machine, and approved flows are shared with your team as an App Skill. - [Ticket pre-test](https://autonom.yatsuk.me/docs/pretest/index.md): Check one ticket and the change behind it on an emulator or Simulator before it reaches QA. Your agent plans the checks, drives them under a budget and hands back a verified pack with a plain verdict. - [Replay](https://autonom.yatsuk.me/docs/replay/index.md): Rebuild the state of a recorded run and stop at the step you want to look at. Replay runs the run's own flow again on your current target, from the start, so your agent can inspect the screen just before or at a failure. - [CI campaigns](https://autonom.yatsuk.me/docs/ci/index.md): Run your flows as one campaign on a CI runner. Autonom keeps every run as a verified report bundle, gates the runs on explicit rules, can publish the whole campaign, and ends with an exit code your pipeline can act on. - [Performance and memory](https://autonom.yatsuk.me/docs/performance/index.md): Measure memory, CPU, frames and traces on the session's device, and tell a growth lead from a real leak. - [Mobile Canvas](https://autonom.yatsuk.me/docs/canvas/index.md): Watch and drive the devices your agent uses, live in a browser tab. Your taps there land in the same journal as your agent's commands. - [Safety and errors](https://autonom.yatsuk.me/docs/safety/index.md): Every failure comes back with a stable code your agent can branch on. Risky steps need consent every time, and credentials are masked before anything reaches disk. - [Capabilities](https://autonom.yatsuk.me/docs/capabilities/index.md): Ask a target what works there before your agent relies on it. One command answers with a snapshot: each capability is available, degraded or unavailable, and anything short of available says why. - [Terms of service](https://autonom.yatsuk.me/docs/terms/index.md): These terms cover Autonom's website, documentation and open-source mobile testing toolkit, maintained by Andrei Iatsuk. Effective October 20, 2026.