Integrations
Verified integrations only
No logo wall of unrelated tools: just the connections RepoFixer actually uses today.
GitHub
RepoFixer connects to a GitHub repository or organization to pull in the work you point it at, run a coding agent against it in an isolated environment, and open a small, human-reviewed pull request back into that repository.
- Connects
- A GitHub repository or organization you authorize.
- Permissions
- RepoFixer only acts on repositories you explicitly connect. Agent execution happens in an isolated environment; see the security page for how that boundary is enforced.
Jira
Jira sync is optional. When connected, RepoFixer can pull tickets from your existing queue so backlog work starts where your team already tracks it, rather than requiring a separate intake step.
- Connects
- A Jira project, for teams that already track backlog work there.
- Permissions
- Jira sync is additive; RepoFixer's core GitHub + agent + PR workflow works without it.
Agent execution options
These aren't connected integrations; they're the coding agents RepoFixer can run a change through once work starts.
Claude
One of the coding agents RepoFixer can run against a ticket. Optional; Claude execution can be disabled without disabling the rest of the product.
Cursor
The other coding agent option RepoFixer can run a scoped change through, isolated the same way regardless of which agent executes it.