Overview - Revyl Documentation

Revyl has two ways of connecting to Cursor depending on use cases. It is recommended to enable both for Cursor developement depending on use case.

	Cursor Plugin	Cursor Cloud Agents
Typical use	Run, verify, and test your app on a live Revyl device while you code	Fix an issue found in Atlas or report/session evidence, or prove changes in a pull request, without leaving Revyl
Direction	Cursor’s editor drives Revyl	Revyl drives Cursor’s cloud agents
Runs in	Your local Cursor Agent chat or Cursor Cloud	Cursor Cloud launched from Revyl

Cursor Plugin

A pinned CLI, skills, and a routing rule that let a Cursor Agent chat run your app on a real cloud device, verify a change, and iterate from the Cursor editor. The plugin does not start an MCP server. Read the Cursor Plugin docs →

Cursor Cloud Agents

Revyl can spawn new Cursor Cloud Agents on your behalf: sending an Atlas screen to a background agent to fix, or handing a pull request’s proof-of-changes check to Cursor. Read the Cursor Cloud Agents docs →

Setting up both

Follow Get Started with Cursor Cloud for the end-to-end walkthrough: connect Cloud Agents, install the plugin, and point proof of changes at Cursor.