Conductor integration. Hand fixes to coding agents in Conductor cloud workspaces.
Praxen Inc. investigates the issue and hands the fix to coding agents in Conductor cloud workspaces, which push the pull request. Bring your own Conductor API key.
Get started for freeWhat Praxen Inc. does with Conductor.
Praxen Inc. investigates, Conductor implements
The investigation ends with a root cause and an evidence trail; Conductor agents take the handoff in cloud workspaces 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 Conductor API key. Praxen Inc. routes the fix through the agent your team already trusts.
How to set up Conductor
- In app.conductor.build, open Users → API keys and create a user-scoped sk_ API key. Your plan must support cloud workspaces.
- Ensure the Conductor account’s GitHub connection can access the target repository.
- Paste the key into Praxen Inc. Review Use Conductor for all autofixes; disable it to use Praxen Inc.’s executor for future fixes instead.
Permissions and access
This credential is user-scoped Conductor API access. The account’s GitHub connection supplies repository access; the connection does not read local desktop workspaces. Praxen Inc. stores the key encrypted and does not expose it to its investigation agent.
Discovery, refresh and the connected view
Praxen Inc. delegates implementation to a coding agent in a Conductor cloud workspace, which pushes the resulting pull request. Sessions use the MCP configuration of the underlying coding harness. For Claude Code, the documented repository file is .mcp.json with mcpServers.praxen, type http, URL https://mcp.getpraxen.app/mcp and bearer authorization. Create the separate Praxen Inc. API key in Settings → Coding agents and supply it through credential configuration, without committing the secret.
Example workflow
Send an investigated repository fix to a Conductor cloud workspace when the team wants its chosen coding harness to do the implementation. Configure that harness’s Praxen Inc. MCP connection so the session can read incidents, the infrastructure graph and observability while working. Review the generated PR in GitHub; repository reachability depends on Conductor’s account connection.
Disconnect and revoke access
Disconnect Conductor in Praxen Inc. and revoke the user API key in Conductor. Also remove separately configured Praxen Inc. MCP credentials and revoke those keys if the coding harness should lose investigation access.
Conductor setup and troubleshooting
Common questions.
Can this connection use a local Conductor workspace?
This integration delegates to Conductor cloud workspaces and requires cloud workspace access on your plan.
Does Conductor use Factory’s MCP configuration file?
No. Conductor uses the underlying coding harness configuration. The documented Claude Code example uses .mcp.json, rather than .factory/mcp.json.