Data and AI releases

2,002 this month · 180 companies

Buildkite, October 2026 new features

19 releases · 1 product · 2 GA

See what's happening across your agents and queues

Buildkite has updated its queue pages to provide better visibility into agent capacity and job status. New charts allow teams to track agent and job activity over time to identify bottlenecks and manage capacity more effectively.

Update
Source ↗

Buildkite Cache is generally available

Buildkite Cache is now generally available, allowing jobs to reuse work such as dependency downloads or build commands. It is integrated into the Buildkite agent and supports custom cache keys and fallback limits.

GA
Source ↗

Filter webhook job events by queue

Buildkite added cluster queue filtering to webhooks in Notification Services and the REST API, allowing job events (scheduled, started, finished, activated, exit status) to be restricted to selected queues.

Update
Source ↗

Configure OpenTelemetry at the cluster level

You can now turn on OpenTelemetry tracing for every agent in a cluster with one setting. Choose an OpenTelemetry notification service in the cluster's settings. Each agent that registers in the cluster then exports traces to that service's endpoint, using its headers, with no OTLP configuration on the agent.

Update
Source ↗

Inspect matrix jobs directly on the build canvas

Matrix steps previously appeared as a single node on the build canvas, with individual jobs shown in a separate panel. Now you can expand them in place to see each job's status and duration, and navigate directly to the job. Similar to group steps , failed matrix steps now start expanded and focus on failed jobs.

Update
Source ↗

Catch pipeline YAML errors before your first build with Buildkite MCP

Your AI agent can now check the pipeline YAML it writes before you commit or upload it. The Buildkite MCP Server includes validate_pipeline , a read-only tool that checks YAML syntax and structure against Buildkite's pipeline schema, without uploading the pipeline or starting a build.

Update

Shipped this week

Buildkite shipped 40 releases. Three themes. Diagnosis. Agents put blocking failures first and retry infrastructure failures. Desktop alerts and log summaries are more reliable. Compatibility. GitHub Actions workflows get hashFiles() in composite actions, Windows checkout fixes, and retries for temporary token failures. Control.

Update
Source ↗

Buildkite MCP Server updates

Your agent can now do more of the work between a failed build and a green one. Here are the latest tool updates for the Buildkite MCP Server . See what changed since the last green build When a build fails, one of the first questions is what's different from the last one that passed. compare_builds answers it in a single call.

Update
Source ↗

Monitor billable active-user usage with the Buildkite API

You can now monitor your organization's billable active-user usage programmatically and compare it with your contracted allowance. Send the count to observability tools such as Datadog to track usage over time, or include it in internal license, billing, and compliance reporting.

Update
Source ↗

Weekly wrap: September 27 – October 3, 2026

What shipped this week Between September 27 and October 3, 2026, we published 4 changelog entries and 35 releases across 13 public repos. Three things run through them: more control and predictability for platform teams, fewer gaps for teams moving off GitHub Actions, and more of the platform agents can drive directly. Tightened how secrets are handled.

Update
Source ↗

Buildkite agent version support policy

From 1 January 2027 , each minor release line of the Buildkite agent will be supported for one year from its first stable release . The final three months are a deprecation period: agents remain supported, with warnings encouraging you to upgrade. Installing an agent or updating to a newer patch doesn't restart that window.

Update