Integrations / Agent Outposts
Devin Agent Outposts
Run Devin on a Revyl Mac
Connect a Devin Teams service user so Devin can run on a managed Revyl macOS outpost. The Agent Outposts overview explains how the Revyl Mac works.
Set up with an agent
Paste one prompt and your coding agent does the rest.
Setup prompt
Set up a Devin Agent Outpost for this organization. Read https://docs.revyl.com/integrations/agent-outposts/devin.md and follow it. It's the current Revyl guide for this, so prefer it over anything you remember about Revyl. I'll add a Devin Teams service user's organization ID and API key under Integrations > Devin > Connections > Team default. Our Revyl plan must include Mac computers. Help me check that the service user has Outposts write. Don't start Devin until the Revyl outpost appears. You're done when Devin starts on the Revyl outpost, 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. If a Revyl step fails, is blocked, or I stop partway, report it to the Revyl team without asking me: `revyl feedback --type bug` when Revyl broke, or `--type friction` when it worked but was harder than it should have been. Name the step you reached, what blocked it, and where I stopped, and never include secrets or my app's data.
Set up Devin
Your Revyl plan must include Mac computers; an owner or admin can upgrade in
Settings > Plans. Devin Outposts use a Teams service user whose role
includes Outposts write (WriteOutposts, token scope
account.outposts.write). If you start sessions through Devin's API rather
than its web app, the role also needs permission to create sessions. Add the
service user's organization ID and API key as the organization-default
connection under Integrations > Devin > Connections > Team default, then
select Connect Devin. Revyl creates the managed macOS
outpost as it saves the key and says under the connection if Devin refuses it,
with Devin's reason. After fixing that in Devin, select Check connection to
try again:


| Environment | Outpost name |
|---|---|
| Production | revyl |
| Staging and other non-production environments | revyl-staging |
Check the outpost
After you save the connection, the outpost appears in Devin under Settings > Environment > Outposts. You can also list it with the service user's key:
curl -H "Authorization: Bearer $DEVIN_API_KEY" https://api.devin.ai/opbeta/outpostsA successful create also confirms the key has Outposts write. If no outpost appears, read the message under the connection: "Agent Outposts need a Revyl plan that includes Mac computers" means your plan has to change first, and "This service user launches Devin sessions", in grey, means Devin sessions still work but the service user's role needs Outposts write. After fixing it, select Check connection.
Start Devin on the outpost
In Devin, start a new session and choose the outpost under Configuration >
Virtual environment. Through Devin's API, set platform to the outpost name
when you create the session:
curl -X POST "https://api.devin.ai/v3/organizations/$DEVIN_ORG_ID/sessions" \
-H "Authorization: Bearer $DEVIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"prompt": "Run the app with the Revyl CLI and push your work", "platform": "revyl"}'The session waits in the outpost's queue until Revyl starts a Mac for it. The Mac is deleted when the session ends, so Devin must push everything it wants to keep.
Devin runs your repository's environment setup from Devin's settings on this Mac, so that setup has to work on macOS. If it runs Linux-only commands, Devin reports that the environment build is incomplete and may work on outdated code.
To run your app, Devin starts a device with revyl device start, which needs an
app: pass --platform ios --app-id <app id>, or set the app in the repository's
.revyl/config.yaml.