Framework

Build for Agents, Not Just Humans

Agents have fundamentally different interface preferences than humans. Designing for both requires treating them as separate audiences.

How it works

  1. 1Humans prefer names. Agents prefer IDs - names create ambiguity when the same pipeline exists across multiple teams.
  2. 2Humans want tables and visuals. Agents want raw, programmatically accessible data they can consume at depth without parsing a display layer.
  3. 3Humans want multi-step flows. Agents want single commands that encapsulate as much as possible - fewer round trips, more efficiency.
  4. 4Bruin tests new CLI tooling by running AI agents against it as if they were human users and benchmarking which interaction model produces faster, more accurate results.
  5. 5Building for agents often produces a product that looks incomprehensible to humans - and that is by design.

Hear it on the podcast

The AI Analyst That Never Sleeps: Burak Karakan of BruinListen to the episode

More from this episode

Get the next framework first

One email a week with the frameworks, tools, and founder stories from the podcast. Free.

More frameworks for AI & Automation