Use Buildkite from Claude
Add the Buildkite connection to a Space that runs Claude, then use it from every channel in that Space.
Create a Buildkite connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Buildkite connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Buildkite connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Buildkite runs continuous integration pipelines on infrastructure a team controls. With a Buildkite connection in type.com, the agent can confirm the scopes on the current API token, list every organization a user belongs to, or check which agents are connected to a pipeline, so engineers can troubleshoot CI access and capacity from the same thread as a failing build.
Connect Buildkite once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Ask the agent to check the current access token's validity and scopes before relying on it for a new automation.
Check the current Buildkite access token's scopes before we wire it into a new deploy pipeline.
Have the agent list organizations tied to the account so a teammate can grab the correct slug for another API call.
List all Buildkite organizations this token belongs to, I need the slug for our main org.
Get the agent to list connected pipeline agents when builds are queuing, to see if more capacity is needed.
List connected Buildkite agents for our main pipeline, builds have been queuing for 20 minutes.
Returns details on the authenticated API token, including its validity and scopes.
Returns Buildkite API metadata, including webhook IP addresses for firewall configuration.
Returns details about the user account that owns the current API token.
Lists every organization the current user belongs to, along with their slugs.
Lists agents connected to an organization, with optional filtering and pagination.
Buildkite provides REST and GraphQL APIs for CI/CD automation, including builds, pipelines, jobs, agents, annotations, artifacts, organizations, teams, clusters, test analytics, package registries, access tokens, CLI API access, Java client support, and hosted or self-hosted build infrastructure workflows.
Yes. With a Buildkite connection shared to a Space, the agent can check token scopes, list organizations, and view connected agents in any thread, visible to the whole team.
Buildkite uses an API key. An admin adds it once when creating the connection and chooses which Spaces can use it, so engineers never paste a token into a prompt.
Yes. A Buildkite prompt can be set up as a type.com automation, such as a daily check of connected agent capacity, posted to a channel.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect Labs64 NetLicensing to Claude in type.com to review products and active licenses from a shared thread.
Connect Langbase to Claude in type.com to manage conversation threads and chunk content for AI workflows in a thread.
Connect Mailtrap to Claude in type.com to clean test inboxes, manage contacts, and export contact data from a thread.
Connect Mapbox to Claude in type.com to batch geocode addresses, look up single places, and run permanent geocodes for stored records.