Internal Agents Map

Mux

Mux gives Coinbase employees a shared interface for working with multiple coding agents concurrently.

Company
Coinbase
Approach type
Platform
Work supported
Coding
Deployment stage
Deployed
Evidence strength
Detailed primary
Entry reviewed
Copy as MDAsk ChatGPT

Capabilities and architecture

Model
Not reported
Harness
Interface for concurrent coding-agent sessions.[Source 1]
Sandbox
Separate worktrees isolate edits; they are not evidence of a security sandbox.[Source 1]
Tool access
Not reported
Knowledge
Not reported
Context management
Not reported
Credentials
Not reported
Interfaces
Not reported

Documented uses

parallel coding sessions → changes reviewed by an employee.

Create workspaces

Each concurrent agent receives its own git worktree, branch and terminal.[Source 1]

Coordinate work

Employees move between agent sessions, review results and provide feedback.[Source 1]

Access and controls

No separate access-control assessment is recorded.

Reliability and validation

Not reported: The available sources do not describe how the team checks the output.

Adoption and operating evidence

These results come from the sources. Notes below each result explain what it covers and any reported limits.

Key observation

Mux: 600+ users including engineers, PMs, and designers (335 active, 197 power users)[Source 1]

Reported by
Coinbase
Scope
Registered Mux users including engineers, PMs, and designers; 335 active and 197 power users

The source does not report the denominator of this figure.

About this result
Category
Adoption output
Evidence type
Reported measurement
What it covers
Mux: 600+ users including engineers, PMs, and designers (335 active, 197 power users)
Key observation

Mux: 5,068 merged PRs across 461 repositories and 10 orgs[Source 1]

Reported by
Coinbase
Scope
Mux merged pull requests across repositories and organizations

The source does not report the denominator of this figure.

About this result
Category
Adoption output
Evidence type
Reported measurement
What it covers
Mux: 5,068 merged PRs across 461 repositories and 10 orgs
Key observation

Mux users show 3.5x more merged PRs per engineer than baseline (39.6 vs 11.4); the post cautions users may skew toward already-high-output engineers[Source 1]

Reported by
Coinbase
Scope
Merged pull requests per engineer for Mux users compared with a baseline of non-users
Denominator
Engineers not using Mux at the time of the comparison (11.4 merged PRs)
About this result
Category
Adoption output
Evidence type
Reported measurement
What it covers
Mux users show 3.5x more merged PRs per engineer than baseline (39.6 vs 11.4); the post cautions users may skew toward already-high-output engineers

Lessons

Not reported: The available sources do not report lessons from this work.

Back to infrastructure
Improve this record

Give your coding agent the context and instructions to prepare a source-backed update.

Paste the prompt into your coding agent, then describe the correction or add a public source.

Preview prompt

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. Coding had a concurrency problem: how Mux helped solve ithttps://www.coinbase.com/de/blog/coding-had-a-concurrency-problem-how-mux-helped-solve-itEngineering blog · First party · Last source verification: 2026-08-31
Question coverage and scope
purpose
Reported
workflow
Reported: Documented use example; no universal platform run is implied.
human involvement
Not applicable: There is no single platform-wide agent review boundary. Scoped downstream operating-model claims remain in research details; access controls are described separately.
implementation
Reported
validation
Not reported
observations
Reported
lessons
Not reported
Research details for every claim on this page
  1. Summary
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  2. Sandbox
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  3. Harness
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  4. Create workspaces
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  5. Coordinate work
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
  6. Key observation
    Statement type
    Metric
    Provenance
    Reported
    Confidence
    Not assessed
    Confidence reason
    No explicit confidence assessment is recorded for this claim.
    Reported by
    Coinbase
    Scope
    Registered Mux users including engineers, PMs, and designers; 335 active and 197 power users
    Denominator
    Not reported
    Method
    Not reported
    Observation date
    Not reported
  7. Key observation
    Statement type
    Metric
    Provenance
    Reported
    Confidence
    Medium
    Confidence reason
    Coinbase reported the aggregate in its own engineering blog without independent verification or a measurement window.
    Reported by
    Coinbase
    Scope
    Mux merged pull requests across repositories and organizations
    Denominator
    Not reported
    Method
    Not reported
    Observation date
    Not reported
  8. Key observation
    Statement type
    Metric
    Provenance
    Reported
    Confidence
    Medium
    Confidence reason
    Self-reported comparison whose own text cautions that Mux users likely skew toward engineers who were already high-output and AI-forward; no cohort method is documented.
    Reported by
    Coinbase
    Scope
    Merged pull requests per engineer for Mux users compared with a baseline of non-users
    Denominator
    Engineers not using Mux at the time of the comparison (11.4 merged PRs)
    Method
    Not reported
    Observation date
    Not reported
  9. Operating model assessment

    Level 3 for parallel coding sessions → changes reviewed by an employee; human attention boundary: work-product review.

    Statement type
    Inference
    Provenance
    Catalog judgment
    Confidence
    Medium
    Confidence reason
    The source documents this scoped human attention boundary; it is not a claim about every system at the company.
    Observation date
    2026