R101 · Infrastructure for agents at scale › Developer infrastructure under agent load

Uber SLATE: agents that test their own changes end to end

Read the original

developer-infrastructurecoding-agentstestingcode-reviewcicost

Source: The Pragmatic Engineer podcast, "Uber's AI infra, from the inside" (Gergely Orosz with Uber Distinguished Engineer Uday Kiran Medisetty, 2026-10-14; summary and transcript). Clip on SLATE posted by The Pragmatic Engineer on LinkedIn, 2026-11-16.

The idea in one paragraph

Uber already had SLATE, a per-engineer staging mechanism: deploy just the services your branch changes into your own short-lived instance, and route your test account's traffic to it, while every other upstream and downstream call goes to shared staging. Uber taught its coding agents to stand up a SLATE instance and gave them the service APIs to drive it. The agent then runs a browser against both main and the branch, produces a before-and-after regression report, and attaches screenshots and video to the pull request. The same pattern exists for iOS, Android and backend APIs. The point is less the tool than the order of work: the agent proves the change works end to end before a human reviews it.

Architecture

  1. Branch-scoped deploy. Only the services touched by the change are deployed into an isolated instance. Everything else stays shared, so the environment is cheap and quick to create.

  2. Identity-based routing. A test account's user ID is routed to the instance; other traffic is unaffected. Distributed tracing (Uber cites Jaeger) is what makes this routing practical across many services.

  3. Agent-driven A/B run. An agent browser exercises the same flows against main and against the branch.

  4. Evidence as an artifact. A diff-style report of behaviour, plus screenshots and video, is attached to the PR, so reviewers see what changed, not just the code.

Where it sits in Uber's wider agent stack (from the same episode)

Why it matters

Tradeoffs

Failure modes to watch

Review checklist for adopting the pattern

Connections

See R101 on the knowledge map

Part of the Research notes on nowucca.com. Figures and claims are the source's own unless the summary says otherwise.