A useful GitHub issue starts with more than a bug title. Gleap sends customer reports to the repository you choose, carrying the report and its captured technical context into your engineering backlog. GitHub issues and Kai Code pull requests are both available on Team, Pro and Enterprise.
From customer report to GitHub issue
Create an issue from an individual ticket, or automatically forward selected ticket types. The integration supports creating and updating issues and sending messages to an issue, so new information can follow the original report. Status and label changes on the issue appear in the Gleap ticket’s history.
For example, your support team can send a confirmed checkout bug to the repository that owns checkout while keeping routine account questions in Gleap.
Connect your repository
- Add GitHub from your project’s Integrations settings and authorize the connection.
- Choose the destination repository.
- Select which ticket types to send automatically, or leave automatic sending off for manual handoffs.
- Send a sample report and check that it reaches the intended repository with the context your team needs.
The issue tracker setup guide covers routing and connection checks. In-app bug reporting explains the evidence Gleap can capture before a report reaches GitHub.
Pull requests from Kai Code
This integration puts work in GitHub Issues. Repositories for Kai Code connect separately: install the Kai by Gleap GitHub app from Kai Code and choose the repositories it can access. From Team, Kai Code opens a pull request for each task it works on, started on its own when you allow it or by your team, from Kai Code Cloud or from the Kai Code Bridge on your own machine, and your engineers review and merge it.
When Kai Support investigates a customer report, it reads the connected GitHub repositories, and cites the files it read. After a merge, the customer follow-up runs with your release settings: by default a teammate confirms the fix is live first.
FAQ
Which Gleap plan includes the GitHub integration?
Team, Pro and Enterprise include the GitHub issue integration and Kai Code, which opens pull requests in your GitHub repositories. See pricing for the plans.
Do GitHub issue changes sync back to Gleap?
Partly. When the GitHub issue is closed or gets a label, the change appears in the Gleap ticket’s history. Comments on the GitHub issue stay in GitHub.
Can Gleap’s AI agents use GitHub through MCP?
Yes, as an agent tool that is separate from this integration. Kai Support and Kai Code can use GitHub on Team, Pro and Enterprise, and custom agents can use it on Team, Pro and Enterprise. Gleap connects the tool through Composio’s MCP server for GitHub, and the agent calls only the actions you switch on. Kai Code does not need it for its own work: it reaches your repositories through the Kai by Gleap app.
