Uber CTO shows how Claude Code can blow up AI budgets
Uber’s chief technology officer has revealed that the ride‑hailing giant’s rapid rollout of AI coding tools, particularly Anthropic’s Claude Code, has forced the company to revisit its 2026 artificial‑intelligence budget after spending more than planned in just a few months. Praveen Neppalli Naga told insiders that engineering teams’ adoption of Claude Code and similar assistants has surged far beyond internal forecasts, with many engineers now integrating these models into daily workflows to generate, review, and refine backend code. The move has delivered speed and productivity gains, but also exposed the steep cost of scaling large‑language‑model usage across thousands of developers.
According to reports drawing on company disclosures and internal commentary, Uber’s AI and software‑development spending is embedded within a broader R&D envelope that reached 3.4 billion dollars in the prior fiscal year. Within that envelope, the portion allocated specifically to AI tools and platform development has been largely consumed in early 2026, driven by token‑based usage fees tied to Claude Code and other coding‑focused models. Engineers were given access to Claude Code in bulk late last year, and usage quickly ramped up, with data indicating that AI‑written or AI‑assisted code now accounts for a rising share of live updates to Uber’s backend systems. This has turned what was initially seen as a supplementary tool into a core, recurring cost center.
Naga described the situation as a “back to the drawing board” moment, emphasizing that Uber did not anticipate the pace at which engineers would embrace AI‑driven coding assistants. He noted that Claude Code has become the dominant tool within the company’s expanding AI toolkit, outpacing other coding‑focused models whose growth has stabilized. The CTO also signaled that Uber is now evaluating additional coding assistants, including OpenAI’s Codex, as it seeks to balance productivity, reliability, and cost control. For the company, the episode underscores the tension between unlocking faster engineering throughput and containing the financial risk of runaway AI‑compute bills.
Analysts point out that Uber’s experience reflects a broader pattern in the tech sector, where once‑modest AI experiments quickly morph into enterprise‑scale deployments with outsized token‑usage profiles. When thousands of engineers regularly invoke models to generate boilerplate, refactor legacy systems, or scan codebases for vulnerabilities, even “small” per‑request fees compound into multimillion‑dollar quarterly bills. The CTO’s remarks imply that Uber will likely introduce more granular cost monitoring, usage quotas, and policy guardrails for AI coding tools, while still preserving their role in accelerating development cycles. For other large employers, the episode serves as a cautionary signal that AI budgeting must now treat language models as permanent infrastructure, not one‑off experiments.
-
08:00
-
07:56
-
07:50
-
07:45
-
07:37
-
07:35
-
07:25
-
07:15
-
07:09
-
07:02
-
07:00
-
17:45
-
17:30
-
17:15
-
17:00
-
16:45
-
16:30
-
16:15
-
16:00
-
15:45
-
15:30
-
15:15
-
15:00
-
14:45
-
14:30
-
14:15
-
14:00
-
13:45
-
13:30
-
13:15
-
13:00
-
12:45
-
12:30
-
12:15
-
12:00
-
11:45
-
11:30
-
11:16
-
11:15
-
11:12
-
11:04
-
11:00
-
10:53
-
10:45
-
10:30
-
10:15
-
10:00
-
09:45
-
09:30
-
09:15
-
09:15
-
09:00
-
08:45
-
08:30
-
08:15
