Give the CLI to your agent. Point Cursor, Claude Code, Codex, or any coding agent at the Revyl CLI and it can create tests, upload builds, drive live devices, and run your suite end-to-end. Point it at your app and let it test.
Why Use the CLI?
- Local-first workflow - Edit tests in your IDE, sync with the cloud
- CI/CD ready - Integrate testing into your build pipelines
- Fast iteration - Run tests directly from your terminal
- Version control - Store test definitions alongside your code
Installation
Install the CLI using your preferred method:- Homebrew remains a good macOS package-manager option when you want updates through
brew upgrade revyl. - The PyPI package is CLI-only and includes the native Revyl binary for the
selected platform. It does not download a binary when
revylfirst runs. - The shell installer downloads the native binary directly. Package-manager installs via pip, pipx, or uv auto-download the CLI binary on first use.
Direct download
Download the binary for your platform from GitHub Releases. Available builds:
After downloading, make the binary executable (macOS/Linux) and place it on your
PATH.
Verify Installation
Run Diagnostics
Check that everything is configured correctly:- CLI version and updates
- Authentication status
- API connectivity
- Project configuration
- Build system detection
Updating the CLI
Use the upgrade command that matches how you installed:revyl upgrade performs a self-update (downloads the latest binary, verifies checksums, and replaces the executable). To check for updates without installing, use:
revyl upgrade performs a Homebrew or direct-download upgrade, it also refreshes existing Cursor, Codex, and Claude Code skill directories with the new embedded Revyl skills. If you update Revyl with a package manager command directly, refresh manually with:
Global Flags
These flags work with any command:Pick Your Path
Each build guide walks you through the exact 2-3 commands to go from your repo to a passing test.
What Happens Next
After picking your framework above, your typical workflow is:- Dev loop —
revyl devconnects a cloud device to your local code with hot reload - Create tests — write YAML test definitions and run them
- CI/CD — run tests on every PR
What You Can Do
Every surface of Revyl is available from the terminal.- Tests: create, sync, edit, and run tests from YAML files stored alongside your code
- Builds: upload iOS and Android binaries, pin versions, sync with CI builds
- Devices: spin up cloud iOS and Android sessions, drive them with tap/swipe/type, set GPS, open deep links
- Dev Loop: iterate on tests with hot reload against a live device
- Workflows: trigger test suites, watch runs, pull results
- Reports: download video, logs, and network traces
- Library: manage modules, global variables, launch vars, scripts, and files
Built for Agents
The CLI is designed to be delegated to an AI agent. Give your agent access to the CLI and it gains full control of your mobile testing stack. What agents can do with Revyl:- Bootstrap a new test suite from scratch by exploring your app on a live device
- Debug failing tests by reading reports, reproducing on a device, and fixing the steps
- Write tests that match feature PRs and add them to your workflow
- Upload builds, pin versions, and trigger regression suites
- Scrape device logs and network traces to root-cause flakes
Key Resources
Authentication
Set up your API key
MCP Setup
Connect Revyl to Cursor, Claude Code, or Codex
Command Reference
Every CLI command and flag
Configuration
Project setup and configuration
CI/CD
Run tests from your pipelines
Dev Loop
Hot reload with live devices
GitHub Repository
Source, releases, and README