Uber open-sourced its security monitoring for Claude Code, Cursor and Codex

Uber open-sourced security monitoring aimed at Claude Code, Cursor, and Codex. The project lives at github.com/uber/ADR. On Hacker News it appeared as item 49197869 with 3 points and 0 comments under the Claude/Codex/Fable thread.

ADR is framed as monitoring for AI coding agents that run with broad local access: editors, shells, and file systems. Claude Code, Cursor, and Codex are named as the targets, so the surface is agent-driven change rather than only human-authored commits. Without published architecture notes, benchmarks, or version pins in the source note, the concrete claim is scope: Uber is sharing how it watches those tools, not a generic app-security kit.

For engineers shipping agent-assisted workflows, that matters because the risk is not only model output quality. Agents can edit, run, and stage changes at speed; security monitoring has to sit next to those loops. An open Uber implementation gives teams a concrete reference for policy, logging, and review hooks around the same three tools many shops already allow.

Market context is crowded on the agent side and thin on shared defensive tooling. Claude Code, Cursor, and Codex compete on speed and capability; Uber’s release is on the control plane: how a large company instruments those agents. Early HN traction is low (3 points, no comments), so this is still a signal post more than a settled standard.

Practical takeaway: open the ADR repo, map its checks to your allowed agent set, and decide what you log, block, or escalate before agents touch production paths. Watch whether other large shops publish comparable agent-security monitors, and whether Claude Code, Cursor, or Codex document first-class hooks that match this kind of monitoring.