Skip to main content
You can use these devices without creating a Revyl test. See Device Infrastructure for custom harnesses, CI workflows, and the Appium and Maestro connection requirements. If you are new, start with Device Quickstart.

Choose Your Path

Device Quickstart

Learn the core session and action loop in minutes.

Auth And Session Prep

How session.before_script and session.auth_bypass attach on revyl device start.

Live Observability

Stream perf, network, and device logs live, and pull post-session artifacts.

Troubleshooting

Fix session, install, grounding, and action issues quickly.

When To Use What

Core Ergonomics Loop

Whether you use CLI, SDK, or MCP, use the same reliable loop:
  1. Take a screenshot or otherwise re-observe current state.
  2. Choose one best action.
  3. Verify the result immediately.
  4. Repeat.
This avoids blind action chains and makes failures easier to debug.

Quickstart

This is the fastest way to get a working device session and take real actions safely.

1. Install and Authenticate

Then authenticate. The CLI prints an approval URL — open it in any browser and approve:
You can also use an API key:

2. Start a Device Session

Run from the directory that owns .revyl/ (or a subdirectory of it) so project config is loaded.
If .revyl/config.yaml declares session.before_script and/or session.auth_bypass, the CLI runs session.before_script and applies session.auth_bypass when each is configured for iOS and Android sessions. Web (alpha) starts do not run session.before_script. See Auth And Session Prep.

3. Install and Launch Your App

Use a direct build URL (APK or IPA). Launch defaults to the app you just installed, so you do not need to know its bundle ID — pass --bundle-id only to launch a different installed app.

4. Use the Safe Action Loop

Always re-observe before and after important actions.

5. Stop the Session

Next