Give a customer a useful update without losing the engineering context. A Gleap Custom Agent connected to GitHub through Composio can use selected tools to read an issue, follow its discussion, and check whether a linked pull request has merged.
Unlike the native GitHub integration, which turns tickets into GitHub issues from your project settings, this Composio toolkit gives Gleap’s AI agents GitHub actions they can call during a run.
Bring the issue back into the conversation
Build a follow-up agent around the repository and issue that belong to the customer’s report. The GitHub toolkit includes tools for retrieving an issue and listing its comments. A separate tool checks the merge status of a known pull request.
Your agent could use those details to prepare an update for support. A merged pull request is one piece of evidence; your release process determines when the fix reaches customers.
Connect the repository context
Add GitHub to your custom agent’s tools and complete the connection flow. Open the connected tool to see the actions available to that account, then disable actions the workflow does not need.
Give the agent the repository owner, repository name, and issue or pull request number. Check a known issue after connecting, particularly when the repository belongs to an organization. The GitHub toolkit reference explains authorization and the individual tools.
Choose the right GitHub workflow
For sending Gleap reports into GitHub Issues, use the native GitHub integration. For turning customer bugs and requests into shipped fixes and features, explore Kai Code. Use a custom agent when you want to design a specific lookup or follow-up around GitHub context.
