Releasesby GlyphRequire SSO sign-in again for your organization
During a suspected security incident, organization administrators can now revoke their organization's SSO sessions without contacting Support. Under Settings → Security , select Require SSO sign-in again to review and confirm the action. This revokes your organization's SSO sessions, including your own.
Also shipped Nov 4, 2026Buildkite in November 2026 →
New embedding models for document indexes
Document indexes can now embed text with three more hosted models: gemini-embedding-2 from Google, and text-embedding-3-small and text-embedding-3-large from OpenAI. Each takes any dimension in a range, up to 3,072, and embeds up to 8,192 tokens per value.
Bots - Granular access controls for the top Personal Agents
The Configure AI bot policies setting is now named AI Crawler and Agent access policies . Personal agents act on a person's behalf, fetching information or browsing in response to a request. The updated policies let you set actions for the top Personal Agents individually.
Claude Code 2.1.318
- Added a record of your answer when Claude Code asks to turn on the mods it writes in a session Added assume_role on mantle upstreams of the Claude apps gateway, for a role in another AWS account and for per-developer AWS cost attribution Added an effort option to a mod's $.model.fork, so a quick side job can run at low whatever effort the session uses...
Claude Agent SDK 0.2.178
Internal/Other Changes Updated bundled Claude CLI to version 2.1.318 PyPI: https://pypi.org/project/claude-agent-sdk/0.2.178/ bash pip install claude-agent-sdk==0.2.178
BYOK and enterprise custom models in the Copilot usage API
The Copilot usage metrics API now shows bring your own key (BYOK) usage across GitHub Copilot, so you can separate it from Copilot-hosted model usage. Reports cover two kinds of BYOK: Local BYOK is configured by developers in their client. Requests go from Copilot CLI or the GitHub Copilot app directly to the developer’s provider key or local model.
Qwen Code Release v0.26.7
Highlights _See the complete change list below._ Breaking Changes No known breaking changes. Complete Change List Features Adds an operator-scoped model.catalogRefresh setting and lets privacy.usageStatisticsEnabled: false stop background catalog refreshes while local metadata remains available.
More from BuildkiteEvery Buildkite release →
Check out GitHub code without long-lived credentials on self-hosted agents
Self-hosted agents can now use temporary, read-only GitHub App tokens for repository checkout. This eliminates the need to distribute and rotate long-lived SSH keys or personal access tokens across your agent fleet.
Trace propagation across triggered builds
Agent spans across your multi-pipeline workflows can now share a single OpenTelemetry trace without contacting Support to enable propagation. Buildkite automatically passes trace context from a parent build to builds it triggers. This also works for internal trigger chains without externally supplied trace context.
A changelog post about the changelog menu
We’ve added a changelog menu to Buildkite. This changelog post is to let you know about the changelog menu, and is available in the changelog menu for that purpose. If you arrived at this changelog post through the changelog menu, you already know about the changelog menu.
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.
Manage Test Engine workflows with Terraform and the REST API
Users can now manage Test Engine workflows using the buildkite_test_suite_workflow Terraform resource or the REST API, enabling code-based configuration of monitors and actions.
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.
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.
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.