Remedy GitHub is one implementation of Git. Remedy is built around the repository itself.
Repair against an authorised repository and exact baseline commit, regardless of where supported Git hosting lives.
Repository sources
The connector architecture is designed to support hosted and self-hosted Git sources, including GitHub, GitLab, Forgejo, Bitbucket and generic Git servers. Individual connector availability must be confirmed during onboarding; the repair model does not fundamentally depend on GitHub.
Exact baseline identity
Remedy associates an incident with repository, branch and exact commit so diagnosis and repair do not drift from the deployed software. A candidate is created in an isolated workspace and recorded as a new source state.
Branches, pull requests and merge requests
Where the repository connector supports it, Remedy can prepare a dedicated repair branch and integrate with the project’s pull or merge request workflow. Customer review and deployment policy remain authoritative.
Self-hosted Forgejo
Forgejo illustrates why provider independence matters: organisations can keep Git on their own infrastructure while still exposing an authorised, auditable repair workflow. A managed Forgejo offering should only be advertised if separately confirmed.
Frequently asked questions
Is Remedy a GitHub-only AI bug fixer?
No. It is designed around mapped Git repositories and exact commits, with provider-specific connectors added where supported.
Is Forgejo support available?
Forgejo is part of the intended repository architecture; production connector availability should be confirmed rather than assumed.
From bug report to verified fix.
See how Remedy connects evidence, diagnosis, repair, deterministic checks and production verification.
Explore the complete workflow →