Gleap AI agents can use Buildkite through Composio, for engineering teams that run CI on their own Buildkite agents and fix bugs customers report in Gleap. The Composio toolkit is small and read-only: a custom agent or Kai Code can list connected Buildkite agents and organizations, but it cannot read builds or logs.
What a Gleap agent can do in Buildkite
- Are the CI agents online: List Pipeline Agents shows which Buildkite agents are connected, for example when the checks on a pull request for a customer’s bug never start.
- Which organization: List Organizations returns the organizations the token’s user belongs to, so queries target the right one.
- A token that only reads: Get Current Access Token shows the scopes of the connected token, so you can confirm the agent’s access is read-only.
- Webhook addresses for your firewall: Get Meta returns the IP addresses Buildkite sends webhooks from, which helps when a firewall blocks them.
Example: checks that never start
Kai Code opens a pull request for a login bug a customer reported in Gleap, but the Buildkite checks stay pending for an hour. The engineer asks a custom agent to find out why. The agent lists the pipeline agents and finds that none are connected for your organization. The engineer restarts the agent hosts, and the checks run.
How to connect Buildkite
- In Gleap, open AI & Automation, then Agents, and select the custom agent that should use Buildkite, or click Create agent.
- Under Tools, click Add tool, search for “Buildkite” and select it.
- Enter a Buildkite API access token and any other details the form asks for, then click Connect Buildkite.
- Open the Buildkite tool and check its five actions; all of them read data.
- Publish the agent and test it in chat. For Kai Code, add Buildkite under Settings, MCP instead.
Kai Code is on Team, Pro and Enterprise, and Kai Support can use connected apps as tools on the same plans. Custom agents are on the Team, Pro and Enterprise plans.
FAQ
Does Gleap integrate with Buildkite?
Yes, with a narrow toolkit. Custom agents and Kai Code use Buildkite through Composio’s Buildkite toolkit, authenticated with an API access token. They read Buildkite data while they run; Gleap does not receive Buildkite events.
What can a Gleap AI agent do in Buildkite?
Five things: list organizations and connected agents, read the current user, read the token’s scopes and read Buildkite’s meta data such as webhook IP addresses. It cannot read builds, jobs or logs, so it does not explain why a build failed.
Which Gleap plan includes the Buildkite integration?
Kai Code can use Buildkite on Team, Pro and Enterprise, and Kai Support can use connected apps as tools in its customer conversations on the same plans. Custom agents that use Buildkite are part of the Team, Pro and Enterprise plans. Give the token read scopes only. AI usage is billed separately; see pricing.
How do we give the agents build logs?
Not through this toolkit today. If your team runs its own MCP server with Buildkite access, you can connect it in Kai Code’s settings or as a custom MCP tool; a custom agent can also call Buildkite’s REST API through an API call tool you configure.
