Abstract
At Uber, more than 70% of pull requests are attributed to coding agents. Engineers use more than 5K agent skills, and all MCP traffic goes through one gateway with more than 1,000 servers. Between February and August 2026, weekly active users of agentic tools grew 7x and weekly agent requests grew 9.4x and since May the spend has stabilized.
This talk describes the methods behind that. We split agent spend into six terms: users, sessions per user, turns per session, requests per turn, tokens per request, and price per token. For price per token, we built the Uber SWE Benchmark from 1,075 merged pull requests and use it to choose a model and reasoning effort for each workload. For tokens per request, we cap context and match prompt cache lifetimes to the workload. For requests per turn, we use tool search and code-mode batching, and we ground agents in a context graph. For turns per session, we show engineers a live cost counter as they work.
Key takeaways
- Split cost into terms you can measure, and give each term a lever.
- Choose models per workload from a benchmark built on your own code.
- Most savings come from agent overhead: fewer turns, fewer requests and fewer input tokens per request.
QCon San Francisco 2026 is a three day conference for senior software engineers, architects and team leads. An international program committee of working engineers selects every session. Patterns and practices, not products and pitches.
Part of the track
Guardrails & Safety Nets for the New Landscape Hosted by Tanya Reilly Principal Engineer @Datadog, Author of "The Staff Engineer's Path"From the same track
Monday 16 November
10:35 Ballroom A Session Running Software Factory Efficiently at Uber Scale: Holding Agent Spend Steady While Requests Grew 9X Uday Kiran Medisetty VP, Distinguished Engineer @Uber At Uber, more than 70% of pull requests are attributed to coding agents. Engineers use more than 5K agent skills, and all MCP traffic goes through one gateway with more than 1,000 servers. 11:45 Ballroom A Session AI How Airbnb Guardrailed Its AI Customer Support Agent Weiping Peng Distinguished Engineer @Airbnb, Previously Principal Architect @Salesforce for AI platform When Airbnb launched its AI customer support assistant, the feature made the news — the guardrails built to make it safe to ship did not. Yet an AI agent that talks to millions of customers, remembers a conversation across turns, and can trigger account actions is a… 13:35 Ballroom A Session Silent Agent Failures: Detect and Fix Them Before Your Customers Notice Diane Lin Staff Engineer @Datadog An agent run can receive a success verdict, complete every tool call without an error, and still fail the customer. It skips a necessary step, cites the wrong evidence, or delivers a confident answer that doesn’t resolve the request. 14:45 Seacliff D Unconference Unconference: Guardrails & Safety Nets 15:55 Ballroom A Session Agentic Trust: Securing AI Agents in Production Amanda Walker Sr. Director, Engineering - Privacy, Safety and Security @Google This session will cover practical measures that you can take now to run agents more securely in production. This will not cover topics like model training and alignment; rather it will focus on deploying an existing agent as safely as possible. 17:05 Ballroom A Session Into the Labyrinth: What Distributed Systems Have Taught Us About Guardrails Akshay Shah Field CTO @Antithesis AI has changed everything about software engineering...or has it? We've spent the past few decades learning how to build web-scale applications: complex, distributed systems that are too complex to fit into one reviewer's brain, but too critical to just YOLO into production.