Devin
Connect
Connect Devin from the terminal. Pass --help for the flags Devin accepts.
polylane integration connect --type devinService user token from the Devin API.
Connect Devin to delegate autofix implementation to Devin cloud agents. Polylane investigates and proposes the fix; Devin opens the pull request on your GitHub. Bring your own Devin API access.
Setup
- In Devin, go to Devin API → Service users and provision a service user.
- Copy its token (it starts with
cog_). - Paste the token into Polylane. The organization is detected automatically.
Connecting makes Devin the executor for every autofix the workspace creates. To route autofixes back through the Polylane executor, turn off Use Devin for all autofixes on the Devin integration page in Settings.
Your token is encrypted before it is stored, and the agent never sees it. Your Devin plan must include API access.
Give Devin Polylane's MCP tools
Devin sessions can query Polylane directly (incidents, investigations, the infra graph, observability) over MCP while implementing a fix:
- In Polylane, open Settings → Coding agents and create an API key. One click creates it with every read scope the MCP tools check.
- In Devin, go to Settings → Connections → MCP servers and click Add a custom MCP (requires the Manage MCP Servers permission).
- Choose the Streamable HTTP transport and set the server URL to
https://mcp.polylane.com/mcp. - Set the bearer token to the API key from step 1. Devin sends it as
Authorization: Bearer <key>.
Disconnecting
Disconnect Devin in Polylane, then revoke the service user token in Devin.
Disconnect
Disconnecting stops every sync and check and deletes the credentials Polylane held. Everything Polylane set up in Devin is removed as well; nothing is left behind.
polylane integration disconnect <id>