Devin integration: connect Devin to Polylane
Connect Devin to Polylane with a service user token. Delegate fix implementation to a Devin session after investigating the incident and review its PR.
Get started for freeWhat Polylane does with Devin.
Polylane investigates, Devin implements
The investigation ends with a root cause and an evidence trail; Devin takes the handoff and opens the pull request on your GitHub.
PRs that link back
Every pull request links back to the investigation that produced it, so the reviewer sees the evidence, not just the diff.
Your key, your account
Bring your own Devin API key. Polylane routes the fix through the agent your team already trusts.
How to set up Devin
- Open Devin API → Service users and provision a service user. Your Devin plan must include API access.
- Copy its cog_ token and paste it into Polylane. Organization identity is detected automatically.
- Review Use Devin for all autofixes. Connecting selects Devin as executor; disable the setting to route future autofixes through Polylane again.
Permissions and access
The service user token authorizes Devin API sessions in your organization. This is implementation delegation, not cloud-resource discovery. Repository access must already be available to Devin. Polylane encrypts the token and keeps it out of the investigation agent’s context.
Discovery, refresh and the connected view
Polylane investigates and proposes a fix, then delegates its implementation to a Devin cloud session that opens a GitHub pull request. Devin can also query Polylane over MCP, but that access needs a separate setup: create a Polylane key under Settings → Coding agents; in Devin Settings → Connections → MCP servers add a custom server, select Streamable HTTP, use https://mcp.polylane.com/mcp and set the bearer token. Managing MCP servers requires Devin’s Manage MCP Servers permission.
Example workflow
Use a Devin session to implement the repository change from a completed incident investigation. Give the session Polylane’s MCP connection so it can look up the affected services and investigation evidence while working. The implementation arrives as a PR rather than requiring the investigation agent to edit production code directly.
Disconnect and revoke access
Disconnect Devin in Polylane and revoke its service user token in Devin. If you separately installed a Polylane MCP server in Devin, remove that connection and revoke its Polylane API key when no longer needed.
Devin setup and troubleshooting
Common questions.
Is a normal Devin login enough to connect?
No. This integration needs a service user token from the Devin API, and your plan must include API access.
Does connecting Devin configure MCP automatically?
No. Add a custom Streamable HTTP MCP server in Devin Connections if sessions should read Polylane context while implementing fixes.