LoginSign Up
← Back to all sparks
B

Buildkite

INFRA · APIS
Velocity8.8

Buildkite ships Agent v4, a VS Code extension, and MCP write-access to secrets in the same week

ci-cddeveloper-toolingmcp-serveride-integrationai-agents
◆Current state
Buildkite is expanding on three fronts simultaneously. Agent v4 — the first major version since 2018 — is now the stable release, clearing eight years of deprecated behavior. The MCP server gained cluster secret creation, test-suite attribution, and build-failure summaries. And a VS Code extension now surfaces pipelines, live job logs, agent status, and YAML validation without leaving the editor.
◆Where it's heading
Two threads are running in parallel: hardening the core agent (v4, ephemeral job acquisition tokens, 1 GiB log quota) and expanding the agentic surface (MCP tools for secrets, test attribution, step uploads, failure summaries). The VS Code extension opens a third front — IDE-native CI — that no major CI platform currently owns. The combination points toward Buildkite positioning as infrastructure for AI-driven developer workflows, not just pipeline execution.
◆Prediction
The MCP server will keep acquiring write operations — secret creation is already there, pipeline modification is the next logical step. The VS Code extension will likely gain pipeline creation and editing to close the IDE-native CI loop.

◆Recent moves

  1. 5d ago

    Buildkite for VS Code

    ⚡ SPARK

    A VS Code extension brings Buildkite directly into the editor — pipeline browsing, agent status, live job log streaming, build notifications, and YAML validation. This is the first first-party IDE integration Buildkite has shipped and places CI visibility where developers already spend their time.

  2. 8d ago

    Buildkite MCP Server updates

    ⚡ SPARK

    The MCP server gained the ability to create cluster secrets alongside new read tools for step uploads, job-state tallies, and test-suite attribution. An agent can now move from observing a failing build to acting on it — creating the missing secret that caused the failure — without a human in the loop.

  3. 13d ago

    Job logs are limited to 1 GiB

    Job logs are now capped at 1 GiB by default, with a cancellation event and timeline entry when exceeded. This is a quota enforcement move — it protects the platform from runaway log-producing jobs while giving teams a clear signal to redirect large output to artifacts.

  4. 14d ago

    Read-only GitHub Actions, Variables, and Environments permissions

    The Buildkite GitHub App now requests read-only access to Actions, Variables, and Environments to support GitHub Actions migration. The change lets Buildkite inspect workflow configuration, variable references, and deployment protection rules without modifying them — a prerequisite for accurate pipeline migration.

  5. 15d ago

    SSH into Linux hosted jobs from the Buildkite CLI

    SSH access to running Linux hosted jobs via the Buildkite CLI extends an existing macOS capability to Linux, letting engineers drop into a live job's shell for interactive debugging. The feature requires the write_builds scope and the organization's remote access setting to be enabled.

  6. 15d ago

    Buildkite Agent v4 is here

    ⚡ SPARK

    Buildkite Agent v4 is now stable and the default for latest/stable channels — the first major version since v3 in 2018. It removes eight years of accumulated deprecated behavior and makes current defaults official, giving the agent a clean architectural baseline going forward.