Factory integration: connect Factory to Polylane
Connect Factory droids to Polylane with your Factory API key. Implement investigated fixes on managed computers and review the resulting pull requests.
Get started for freeWhat Polylane does with Factory.
Polylane investigates, Factory implements
The investigation ends with a root cause and an evidence trail; Factory droids take the handoff on managed computers and push the pull request.
PRs that link back
Every pull request links back to the investigation that produced it, and a PR closed without merging is a tracked outcome, not a mystery.
Your key, your account
Bring your own Factory API key. Polylane routes the fix through the agent your team already trusts.
How to set up Factory
- Create an fk- key in Factory Settings → API keys. Your plan must include API and remote workspace access.
- Confirm the Factory organization’s GitHub connection can access the repositories you intend to fix.
- Paste the key into Polylane. Review Use Factory for all autofixes: connecting selects Factory as executor; disable it to return to Polylane’s executor.
Permissions and access
The key authorizes Factory API work using your own Factory account. Repository access comes from the Factory organization’s GitHub connection. It does not grant Polylane new access to arbitrary repositories or provide a local editor connection. The stored key is encrypted and is not shown to the investigation agent.
Discovery, refresh and the connected view
A Factory droid implements the proposed fix on a Factory managed computer and pushes the pull request. To let droids read production evidence, create a Polylane API key under Settings → Coding agents, then configure the Polylane HTTP MCP server in .factory/mcp.json. Its mcpServers.polylane entry uses type http, URL https://mcp.polylane.com/mcp and an Authorization bearer header. Supply the key through your credential configuration rather than committing it to source control.
Example workflow
Delegate a fix after tracing an incident to a repository accessible by the Factory organization. The droid works on its managed computer, can consult Polylane’s incident and graph tools if MCP is configured, and pushes the implementation for GitHub review. Check the organization’s repository connection when a droid cannot reach the target code.
Disconnect and revoke access
Disconnect Factory in Polylane and revoke the fk- key in Factory. Separately remove a manually configured Polylane MCP credential and revoke its API key if droids should no longer query production context.
Factory setup and troubleshooting
Docker context deadline exceeded
Common questions.
Where does a Factory fix run?
On a Factory managed computer using a droid, with access supplied by your Factory organization’s GitHub connection.
Which MCP configuration do Factory droids use?
The documented repository configuration is .factory/mcp.json with an HTTP Polylane server and bearer authorization. MCP access uses a separate Polylane key.