Changelog

bb agent fix reproduces a failure from a previous invocation and fixes it by editing the current working tree.

The agent reruns the invocation's original Bazel command to reproduce the failure, inspects the failure output and relevant source code, applies a minimal fix, and reruns the command to verify the fix is valid.

When run locally, the changes are applied to the current working tree. When run remotely, the diffset is uploaded to the 'Artifacts' tab of the remote agent fix run. It can be fetched from the invocation using the GetInvocation API and applied to a local workspace using git apply <DIFF_FILE>.

Run it from the workspace that produced the failure, with an invocation ID or URL:

# Fix every failing target in the invocation.
bb agent fix <INVOCATION_ID>

# Fix only a single failing target, or only the test cases matching a filter.
bb agent fix <INVOCATION_ID> //foo:bar_test --test_filter=TestBaz

See the documentation for more details.

You can now use the bb CLI to analyze a Bazel timing profile with an AI coding agent using bb agent analyze-profile.

The command downloads the timing profile for an invocation and returns a detailed report with actionable recommendations for speeding up the build.

The command accepts an invocation ID or URL:

bb agent analyze-profile <INVOCATION_ID>
bb agent analyze-profile https://app.buildbuddy.io/invocation/<INVOCATION_ID>

The command supports interpreting the timing profile with --agent=codex or --agent=claude. If available, it uses your locally authenticated Claude Code or Codex subscription. Otherwise you can set the environment variable ANTHROPIC_API_KEY or CODEX_API_KEY to authorize API requests. You can also specify --model and --effort to control the agent's behavior.

bb agent analyze-profile --agent=codex --model=gpt-5.4 --effort=high <INVOCATION_ID>

See the bb agent analyze-profile documentation for more details.

BuildBuddy now exposes an MCP endpoint for coding agents and other MCP-capable clients.

MCP provides a way to let agents explore BuildBuddy data for mostly read-only workflows like build and test metadata, logs, artifacts, target statuses, and more.

You can connect agents like Codex, Claude Code, and Gemini CLI to:

https://YOUR-BUILDBUDDY-ORGANIZATION.buildbuddy.io/mcp

Authenticate with:

Authorization: Bearer <api-key>

See the new BuildBuddy MCP Server docs for setup instructions and configuration examples.