Dome Systems
Dashboard
DocsLearnHands-on LabsTemplatesHelpChangelogCLIAPIMCPSDKs

Ask questions about Buildkite

A read-only managed agent for Buildkite pipeline investigation.

User
Caller
  • chat
App
Agent
  • buildkite-answerer
Governance
Gateway
  • buildkite-readonly
Pool

buildkite-answerer-pool

  • buildkite-answerer-model
Tools

buildkite

    What this template gives you

    • Interface

      A chat window, in your browser

      Use the included interface to send a request to this template.

    • Gateway

      buildkite-readonly gateway

      This template sends its requests through buildkite-readonly gateway, where its access rules and limits apply.

    • Model

      buildkite-answerer-model

      This template uses buildkite-answerer-model through the buildkite-answerer-pool pool.

    Usage

    Hand this template to an AI agent to set up this template

    Node.js and npm to run npx.

    Dome CLI, installed with brew install dome-systems/tap/dome, then signed in with dome auth login.

    Docker Compose to run the companion app locally.

    1. 1

      Create a workspace

      dome workspaces create --name <workspace-name>

      The CLI creates and selects a workspace context for you.

    2. 2

      Confirm the workspace context

      dome context list

      The workspace you just created is already selected.

    3. 3

      Pull the template

      npx @domesystems/templates pull dome-systems/ai-agent-for-buildkite@0.1.0 --dir ai-agent-for-buildkite

      Downloads this immutable release and verifies its digest.

    4. 4

      Run the template

      npx @domesystems/templates up --dir ai-agent-for-buildkite

      Imports it into Dome and starts the companion app.

    Dome import variables

    npx @domesystems/templates up imports the template into Dome and prompts for required values. For unattended runs, set them as DOME_IMPORT_VAR_… environment variables.

    Required values

    • DOME_IMPORT_VAR_anthropic_api_key

    Setup guide

    Follow this template's setup guidance for agent variables and upstream connections.

    # Configure Buildkite

Buildkite's hosted read-only MCP endpoint uses OAuth with Dynamic Client
Registration. This template uses `https://mcp.buildkite.com/mcp/readonly`, so
the upstream server issues read-only MCP permissions after consent.

- `anthropic_api_key`: enter the Anthropic key used by this agent's model.
- After import, start the shared Buildkite OAuth connection, sign in as a
  dedicated test user, select the intended organization, and approve consent.
- Verify a known test build is visible and that a build in an unshared pipeline
  is unavailable. Build creation, retry, cancellation, and other write tools
  should not be present.

For a headless service that cannot complete OAuth, Buildkite supports API-token
pass-through at `https://mcp.buildkite.com/direct`. That is a separate,
token-based connection—not this OAuth template.

    Runtime environment

    These variables are required to run the agent. During pull, .env.example is copied to .env when available. If they’re missing, npx @domesystems/templates up retrieves them from Dome and saves them in .env. Pass --provision to refresh them.

    No .env.example is included in this release.

    Agent instructions

    Summarize Buildkite pipelines, builds, jobs, artifacts, and failures. Do not trigger,
cancel, retry, or modify builds, pipelines, teams, or organization settings.