Ask HN: AI Agents vs. Gateways vs. Harnesses
TL;DR
A Hacker News thread calls out the messy terminology in the AI agents ecosystem and proposes a cleaner taxonomy.
Key Points
- The core complaint: almost everything gets labeled 'Agent', even products that only implement one narrow slice of the stack.
- The thread explores whether terms like 'Orchestrator' or 'Runner' would be more precise and where the real architectural boundaries sit.
Nauti's Take
The thread is symptomatic of a broader problem: the AI industry names things for marketing value, not technical function, then acts surprised when nobody can orient themselves. The proposed three-way split – Harness / Gateway / Sandbox – is pragmatic and immediately useful, even if still rough around the edges.
What it misses is a dedicated category for true orchestration logic: the layer that coordinates multiple agents, manages state, and handles failures. Frameworks like LangGraph or Temporal belong there but barely get a mention.
Until the industry converges on shared vocabulary, the only fix is doing your own layer-by-layer audit before buying into any 'agent' platform.
Sources