Don't Build Agents You Can't Explain
addyosmani · x · 2026-07-16
In his closing keynote, Addy Osmani emphasized: do not build Agents you cannot take responsibility for explaining.
Key points include:
- Roles/titles < system ownership: Rather than giving someone an "AI-flavored" job title, it is more important to clarify who is accountable for the system's outcomes.
- Quoting Mitchell Hashimoto: when the "speed of generation" exceeds the "speed of understanding," the scarce resource becomes evidence-based judgment.
- His proposed new rule is: "Explain it, or don't ship it."
The post focuses less on specific tools and more on accountability, judgment, and explainability in Agent products and team practices.
Related event: Addy Osmani: Engineers Must Be Accountable for Agent Systems(3 posts)→
More from coding & agent
- Building a Secure AI Agent Gateway: Self-Hosting OAuth for Multiple SaaS Apps — Defiant_Cod_2654 · 2026-07-22
- Rowboat launches as an open-source, local-first AI coworker with memory — ycombinator · 2026-07-22
- Scoble says AI “loops” really means long-running multi-agent workspaces — Scobleizer · 2026-07-22
- Kimi Code opens a waitlist as Moonshot rolls out its coding product — Fabulous_Bonus_8981 · 2026-07-22
- Open-source runtime lets each repo define its own AI code reviewer — ibabufrik · 2026-07-22
- Indie Dev Asks: What's Actually Broken in Your AI Agent's Memory Today? — AcceptableTime7937 · 2026-07-22