Skip to main content
Revyl can hand work to a Cursor Cloud Agent on your behalf: fixing a bug found on an Atlas screen, or proving that a pull request behaves as expected. The agent runs in Cursor’s cloud, but it gets a Revyl credential so anything it builds, tests, or runs on a device is attributed back to the conversation in Revyl.
This is the platform integration under Integrations > Cursor. Looking for the Cursor IDE plugin that lets a Cursor Agent chat drive Revyl devices from your editor? See Cursor Plugin. For a side-by-side comparison, see the Cursor overview.

​
What it does

  • Send Atlas screens to a Cursor cloud agent. From an app’s Atlas screen, users can iterate on and modify their screens by sending screens and surrounding metadata to Cursor. You describe what you need done, and Revyl submits it as a new Cursor Cloud Agent conversation.
  • Track the conversation from Revyl. Every launch shows up under Cloud Agents in the sidebar, with a history list and a detail page per conversation.
  • Let Cursor prove pull requests. Revyl’s GitHub integration can run proof of changes on every PR using the Cursor Cloud Agent harness. In this mode, when a PR is opened, Revyl uses Cursor to verify changes on a Revyl cloud device and posts its findings as the PR comment.

​
Setup

​
1. Get a Cursor API key

Revyl needs a Cursor API key that can launch Cloud Agents. Create a user key at cursor.com/dashboard/api.

​
2. Connect Revyl to Cursor

Go to Integrations > Cursor. There are two independent connection slots:
  • Personal key — runs cloud agents as you. Only you can use it.
  • Team default — shared with everyone in your org; owners and admins manage it. Useful for members without a personal Cursor account.
Paste the key into a slot and click Connect Cursor. Revyl stores it encrypted and never shows it again. Use Check connection any time to verify it against Cursor. If you’re setting up the team default, also turn on Team follow-ups in Cursor’s own Cloud Agent settings so anyone in your org can pick up a conversation Revyl started.

​
3. Launch from an Atlas screen

Open an app’s Atlas, pick a screen, and click Send this screen to.. and select Cursor. Confirm or adjust the pre-filled repository, branch or pull request, and model, describe what you need done, and submit. The new conversation appears under Cloud Agents.

​
4. Configure proof of changes

Turn on proof of changes on a connected GitHub repository, then set its harness to Cursor:
  • In the dashboard, open the GitHub integration page, and select the repository’s PR-review settings and set the Agent selector to Cursor.
  • Click Authorize Cursor proof runs in the repository’s proof settings. This records that proof runs act under your Cursor connection.
Your connection needs access to that repository in Cursor itself, or the authorize step is blocked. See Choose which agent proves the change for the full authorization and fallback behavior.

​
Managing the integration

  • Disconnect: remove a key from Integrations > Cursor. Revyl stops being able to launch agents with that slot; conversations already launched are unaffected.
  • Reconnect: when a slot shows Needs reconnect, paste a new key. The connection identity stays the same.
  • Repository access: the connecting Cursor account must have access to a repository in Cursor itself before Revyl can launch agents against it or authorize it for proof runs. Grant access in Cursor first if a repository or authorization is blocked.
  • Atlas — where Cursor cloud agent launches start
  • GitHub — pull request previews and the Cursor proof harness
  • Cursor proof (BYO-CI) — Automations + your CI upload, without the Revyl GitHub App
  • Cursor Plugin — drive Revyl devices from inside Cursor’s editor
  • Cursor overview — plugin vs. cloud agents, side by side