← All implementations

Block · Orchestration system

Builderbot

A multi-agent orchestration layer built on goose + MCP that coordinates agents across Block's entire codebase, invoked in Slack to take a ticket end-to-end to a reviewed PR.

1 Supports2 Supports3 Contextualizes4 Contextualizes

Approach type
Orchestration system
Work
Coding, Code review
Human involvement
Drafts reviewed
Invocation
Event driven, Interactive
Interfaces
Slack, Linear, Jira, Github
Deployment stage
Scaled
Evidence strength
Detailed primary
Entry reviewed

How it works

The workflow the sources report for this implementation.

Coordinates multiple agents over one codebase instead of running a single loop

1

Linear/Jira ticket -> branch -> code -> PR -> CI watch, end to end

1

Where people stay involved

  • ticket → reviewed pull requestWork product review · Level 3

Level 3 for ticket → reviewed pull request; human attention boundary: work-product-review.

1

Observation date
2026-06-21

Implementation details

Sandbox

unknown

1

Harness

Multi-agent orchestration built on goose (open-source agent framework) + MCP; multi-player, real-time, operating inside Slack threads

1

Model

goose framework; model not specified

1

Interfaces

slack, linear, jira, github

1

Tool access

MCP connects agents to internal tools and data; picks up Linear/Jira tickets, creates the branch, writes code, opens the PR, watches CI

1

Knowledge

Company-wide code context across hundreds of millions of lines and hundreds of services; Block also frames Builderbot as an 'agentic protector' around its software world model

1 Supports2 Supports

Reported results and limitations

The catalog records what the sources report, with the scope and the denominator of every figure. A qualification below limits the figure it sits under.

Reported metrics

Headline claim

~1,500 PRs merged per week (~15% of all production code changes at Block)

1

Reported by
Block
Scope
Builderbot merged pull requests per week at Block
Denominator
All production code changes across Block for the approximately 15% share
Key observation

200,000+ operations per day

1

The source does not report the denominator of this figure.

Reported by
Block
Scope
Builderbot operations per day; the article does not define an operation
Key observation

~1,500 pull requests merged per week (~15% of all production code changes at Block)

1

Reported by
Block
Scope
Builderbot merged pull requests per week at Block
Denominator
All production code changes across Block for the approximately 15% share

Reported outcomes and statements

Key observationOpinion

"What used to take months now takes days"

1

Scope
Reported turnaround for Square seller features and repetitive engineering work

Lessons and interpretation

Concentrate investment on orchestration, context, and the environment; let engineers focus on the problems worth solving

1

Meet people in Slack: tag @builderbot with a short description and it works in the thread

1

Multi-player real-time collaboration lets humans steer research, planning, and implementation rather than only reviewing after the fact

1

Sources and research details

Citations link to the original publisher. Each source also keeps a preserved copy in the repository, so a changed or removed page stays checkable.

  1. Block rolls out Builderbot, a new suite of AI-native tools that changes the way we shiphttps://block.xyz/inside/block-rolls-out-builderbot-a-new-suite-of-ai-native-tools-that-changes-the-way-we-shipEngineering blog · First party · Last source verification: 2026-08-31
    Preserved copy ↗
  2. Protecting our systems with intelligence (Builderbot architecture)https://engineering.block.xyz/blog/protecting-our-systems-with-intelligenceEngineering blog · First party · Last source verification: 2026-08-31
    Preserved copy ↗
  3. block/builderbot source repositoryhttps://github.com/block/builderbotRepository · First party · Last source verification: 2026-08-31
    Preserved copy ↗
  4. Hacker News discussion of the Builderbot announcementhttps://news.ycombinator.com/item?id=48618973Hn thread · Community · Last source verification: 2026-08-31
    Preserved copy ↗
  5. Hacker News comment that points to the Builderbot repositoryhttps://news.ycombinator.com/item?id=48619052Hn comment · Community · Last source verification: 2026-08-31
    Preserved copy ↗
Research details for every claim on this page
  1. Summary
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  2. Headline claim
    Statement type
    Metric
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
    Reported by
    Block
    Scope
    Builderbot merged pull requests per week at Block
    Denominator
    All production code changes across Block for the approximately 15% share
    Method
    Not reported
    Observation date
    Not reported
  3. Sandbox
    Statement type
    Inference
    Provenance
    Catalog judgment
    Confidence
    Medium
    Confidence reason
    The preserved sources do not document an execution sandbox; unknown does not mean absent.
  4. Harness
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  5. Model
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  6. Interfaces
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  7. Tool access
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  8. Knowledge
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  9. Supporting component
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  10. Supporting component
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  11. Key observation
    Statement type
    Metric
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
    Reported by
    Block
    Scope
    Builderbot operations per day; the article does not define an operation
    Denominator
    Not reported
    Method
    Not reported
    Observation date
    Not reported
  12. Key observation
    Statement type
    Metric
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
    Reported by
    Block
    Scope
    Builderbot merged pull requests per week at Block
    Denominator
    All production code changes across Block for the approximately 15% share
    Method
    Not reported
    Observation date
    Not reported
  13. Key observation
    Statement type
    Opinion
    Provenance
    Reported
    Confidence
    Low
    Confidence reason
    Qualitative company statement, not a measured before-and-after study.
    Scope
    Reported turnaround for Square seller features and repetitive engineering work
  14. Lesson
    Statement type
    Inference
    Provenance
    Catalog judgment
    Confidence
    Medium
    Confidence reason
    The catalog derives this observation from the linked sources.
  15. Lesson
    Statement type
    Inference
    Provenance
    Catalog judgment
    Confidence
    Medium
    Confidence reason
    The catalog derives this observation from the linked sources.
  16. Lesson
    Statement type
    Inference
    Provenance
    Catalog judgment
    Confidence
    Medium
    Confidence reason
    The catalog derives this observation from the linked sources.
  17. Operating model assessment
    Statement type
    Inference
    Provenance
    Catalog judgment
    Confidence
    High
    Confidence reason
    The source explicitly describes end-to-end implementation ending in a reviewed pull request.
    Observation date
    2026-06-21

The catalog records no related implementation for this entry yet.

Back to the directory →