Skip to main content
Book a demo

Connect Buildkite to VS Code

Give VS Code governed access to Buildkite’s 71 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo VS Code setup guide

Set up

Add Buildkite to VS Code in four steps

Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.

  1. 1

    Approve Buildkite in Runlayer

    Add Buildkite from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Buildkite’s 71 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code setup guide
  3. 3

    Sign in to Buildkite

    Sign in the way Buildkite requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Buildkite from VS Code

    Buildkite’s approved tools appear in VS Code. Every call is checked against policy and recorded.

Tools

71 Buildkite tools in VS Code

Runlayer policy decides which of these VS Code users can call.

  • Access token

    Get information about the current API access token including its scopes and UUID

  • Cancel build

    Cancel a running build on a Buildkite pipeline

  • Compare builds

    Compare step outcomes, final-attempt retry counts and execution/scheduling times between builds in one pipeline.

  • Create annotation

    Create an annotation on a build or specific job.

  • Create build

    Trigger a new build on a Buildkite pipeline for a specific commit and branch, with optional environment variables, metadata, and author information

  • Create cache registry

    Create a cache registry in a cluster.

  • Create cluster

    Create a new cluster in an organization

  • Create cluster queue

    Create a new queue in a cluster

See all 71 Buildkite tools

Control

What Runlayer can see and stop in VS Code

Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.

  • Gateway policy (available)

    Every Buildkite call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, VS Code as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before VS Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination