> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revyl.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Two ways Revyl and Cursor connect: from the editor, and from the platform

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](/integrations/cursor/plugin)                         | [Cursor Cloud Agents](/integrations/cursor/cloud-agents)                                      |
| ----------- | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| Typical use | Run, verify, and test your app on a live Revyl device while you code | Fix a bug found on an Atlas screen, 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

An MCP server, skills, and a routing rule that let a Cursor Agent chat run
your app on a real cloud device, verify a change, and iterate on the change from the Cursor editor. This is installed directly within Cursor. [Read the Cursor Plugin docs →](/integrations/cursor/plugin)

## 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 →](/integrations/cursor/cloud-agents)