Autonom documentation

Quick start

Four steps in a terminal, then your agent takes over.

1. Get the code.

   Clone the repository and step into it.

   git clone https://github.com/aiatsuk/autonomcd autonom
2. Install it.

   A checklist asks which device tools to add. Tick your agents too, and each one gets the skills.

   ./install.sh
3. Ask what this machine can do.

   Green means installed, not proven. Anything missing comes with the exact fix.

   autonom doctor
4. Take the tour.

   Start a new agent session so it loads the skills. Then take the guided walk on your device.

   autonom tour

Your first check →

Topics

Six groups, in the order you are likely to need them.

1. Start

   Install Autonom, run a first check and learn how your agent owns a device.

   • New to Autonom? Start with your first checkPoint your agent at a Simulator or emulator and get back screenshots and a journal.Start here
   • InstallPut the command line on your PATH and give your agent the skills.
   • Sessions and targetsOwn one device at a time and read every step back.
   • Skills and routingSee which skills your agent loads for Flutter, native Android or iOS.

2. Drive

   Read the screen and act on it by what each element says.

   • Read and drive the screenFind, tap, type and swipe by label.
   • Device stateOpen deep links, set permissions and location.

3. Observe

   Keep what proves a change, and see what the app sent.

   • EvidenceTake screenshots, recordings, logs and crash reports.
   • NetworkCapture and mock requests, only with your consent.

4. Automate

   Save a check once and replay it on every change.

   • FlowsWrite a check as a YAML file and run it again.
   • App memoryKeep notes and runbooks for each app.

5. Go further

   Measure the app, and watch the device in your browser.

   • Performance and memoryMeasure memory, CPU, frames and traces.
   • Mobile CanvasMirror and lightly control a device in your browser.

6. Reference

   Look up an error code and what consent covers.

   • Safety and errorsBranch on a stable error code, with a hint and exit code 2.

How Autonom works

• Skills and one command line. Your agent loads skills that say what to do, and runs autonom, a command line that answers in JSON. No MCP server is needed.
• One explicit target. A session owns one device. With more than one ready, your agent names the one it means, or gets an error listing the candidates.
• The evidence ladder. Your agent climbs from code and tests to the screen, logs, performance and a before and after replay.