angtly · HackerTrans

vor 4 Monatendiscuss

Stateful agents are the next frontier. Once an agent maintains state across sessions, it becomes a persistent service rather than a one-shot tool. And persistent services should be able to charge for their work.

The interesting question is what happens when your stateful agent needs capabilities it doesn't have. Your dev agent needs web search, your research agent needs code execution. Today you build all of that in-house. But imagine a world where your agent just hires a specialist agent for $0.002 per call, gets the result, and moves on.

Microservices solved this for traditional software. The agent equivalent is coming.

angtly

vor 4 Monatendiscuss

The novel patterns angle is interesting. One pattern I keep seeing missing across all agent setups is the economic layer. Every agent framework solves orchestration well, but none of them answer: what happens when Agent A needs to hire Agent B for a capability it doesn't have?

  Right now the answer is "build it yourself" or "use a free API and hope it doesn't break." If specialist agents (search, code exec, PDF parsing) could be hired on-demand with
  per-call billing, you'd see much more composable architectures. The orchestrator focuses on its core logic, and outsources commodity capabilities to paid specialists.

The economics only work on L2s where settlement is sub-cent. That's the unlock nobody's building for yet.

angtly

vor 4 Monatendiscuss

[dead]

comments