Agent Outposts - Revyl Documentation

An Agent Outpost gives a Cursor or Devin Cloud Agent its own temporary Revyl Mac. The agent can build and test your code there, use the Revyl CLI, and start an iOS or web session on that same Mac with revyl device start. The Mac is destroyed when the session ends, so the agent must push every change it wants to keep.

Agent Outposts must be enabled for your organization. Email support@revyl.ai to request access before you configure a vendor connection.

Agent Outposts are in alpha and may change.

Set up with an agent

Paste one prompt and your coding agent does the rest.

Setup prompt

Set up an Agent Outpost for this organization.

Read https://docs.revyl.com/integrations/agent-outposts.md and follow it. It's the current Revyl guide for this, so prefer it over anything you remember about Revyl.

I'll ask Revyl Support to enable Agent Outposts and add a service-account key under Integrations > Cursor > Connections > Team default. Help me check the Cursor prerequisites. Don't start an agent until access is confirmed and the Revyl pool appears.

You're done when the agent starts on the Revyl pool, can run the app with the Revyl CLI, and pushes its work before the session ends.

Ask me before anything that needs my login or approval.

How it works

Revyl adds a private worker pool to your connected Cursor account, or an outpost to your connected Devin account. Each agent you start there gets its own Revyl Mac to work on, with the Revyl CLI ready to build, test, and run your iOS or web app.

Illustration of an agent chat that starts an iOS simulator with revyl device start, beside a Revyl computer tab showing the whole Mac screen with the simulator open — Illustration: the agent's Revyl computer open beside the Cursor agent chat.

Choose your agent

Cursor

Connect a Cursor service account and start a Cloud Agent on the Revyl pool.

Devin

Connect a Devin Teams service user and start Devin on the Revyl outpost.

If setup or start fails

If your organization has reached its Revyl computer limit, Revyl cannot allocate another Mac and the request fails with an error in Cursor. A failed Mac or worker setup also fails the Cursor request rather than silently restarting it. Free a computer or resolve the reported problem before trying again. If the pool never appears, check the service-account key and permissions, then contact Support.

Cursor Cloud Agents — launch agents from Revyl and configure the Cursor integration
Cursor overview — compare the Cursor plugin with Cursor Cloud Agents
Devin — the Devin integration

How it worksCopy Anchor Link

Choose your agentCopy Anchor Link

If setup or start failsCopy Anchor Link

RelatedCopy Anchor Link

On this page

How it works

Choose your agent

If setup or start fails

Related