Conductor
Connect
Connect Conductor from the terminal. Pass --help for the flags Conductor accepts.
polylane integration connect --type conductorAPI key from your Conductor account.
Connect Conductor to delegate autofix implementation to coding agents in Conductor cloud workspaces. Polylane investigates and proposes the fix; a Conductor agent implements it in a cloud workspace and pushes the pull request. Bring your own Conductor API access.
Setup
- In Conductor, go to app.conductor.build → Users → API keys and create a user-scoped API key (it starts with
sk_). - Make sure the Conductor account's GitHub connection has access to your target repositories.
- Paste the key into Polylane.
Connecting makes Conductor the executor for every autofix the workspace creates. To route autofixes back through the Polylane executor, turn off Use Conductor for all autofixes on the Conductor integration page in Settings.
Your key is encrypted before it is stored, and the agent never sees it. Your Conductor plan must include cloud workspace access.
Give Conductor Polylane's MCP tools
Conductor sessions use the MCP configuration of the underlying coding harness, so a server committed to the repository is picked up automatically. Create an API key in Polylane under Settings → Coding agents (one click, every read scope the MCP tools check), then commit .mcp.json (Claude Code format) to the repository:
{
"mcpServers": {
"polylane": {
"type": "http",
"url": "https://mcp.polylane.com/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}
Disconnecting
Disconnect Conductor in Polylane, then revoke the API key in Conductor.
Disconnect
Disconnecting stops every sync and check and deletes the credentials Polylane held. Everything Polylane set up in Conductor is removed as well; nothing is left behind.
polylane integration disconnect <id>