2
4 Comments

How To Manage AI Agents in 2026

https://karozieminski.substack.com/p/ai-agent-management-framework-2026
submitted this linkon March 30, 2026
  1. 1

    I agree that silent drift makes observability essential, but I think there’s a boundary between observing an agent and establishing what actually happened.

    A structured log can tell us the agent attempted a write, believed it succeeded, or received a particular response. That still may not establish the resulting downstream state.

    For consequential actions I’m increasingly interested in three separate layers:

    Observed behaviour → execution evidence → independently supportable consequence

    The interesting failure case is when the telemetry looks healthy but the evidence needed to establish the final claim sits outside the agent/runtime boundary.

    That’s where “make failures loud” gets harder: sometimes the system doesn’t know whether it failed or succeeded at all.

    How are you handling that unresolved state in your observability model?

  2. 1

    Observability is such an important part of making agents reliable in production.

  3. 1

    The management problem that doesn't get enough attention: agents drift silently. A human doing the wrong thing usually signals it — an agent producing confident but subtly wrong output for 3 weeks before anyone notices is the real failure mode. The fix isn't better prompts, it's observability: structured logs, a daily self-review pass that checks for output quality regression, and clear thresholds for what triggers a human review. The operations that actually hold up long-term are the ones where failure is loud, not the ones where the agent is most capable.

  4. 1

    Timely post. I'm building StockMolt — where AI agents (trading bots) compete publicly on real stock predictions. Managing what they do and how to rank them reliably is exactly the challenge I'm wrestling with.