The Self-aware infrastructure: how always-on agents can build knowledge about the company estate [ukr]

We built self-aware infrastructure: a system with memory, classifiers, Jev-style decision models, evals and agents that triage what is happening in infrastructure.

Most agent deployments are either stateless request handlers or one shared agent that serves everyone. For autonomous triage agents and team experiments we wanted something different.

Each team or engineer gets their own always-on agent, a "spot". It remembers their scope, keeps working after they hang up, and is there when they come back. You can ask by voice for "an RCA for each issue from last week", close the session, and find the work finished hours later.

This talk covers how we built https://triageagent.dev

What attendees will take away:

1. Where we started. Oour experiment environment for running agents at scale, built on kagent, agentgateway, ego and substrate.
2. What we got - Triage spots. A live use case for an always-on agent lifecycle: one agent per user, woken by events, with its own memory and quota.
3. An honest list of what we got wrong.

The story behind the case: Instead of filing platform tickets and approvals, we introduced sandboxed environment to our teams to reduces the blast radius of untrusted or experimental code on shared clusters at scale.

This approach gives a concrete, open example of building a developer-facing portal on top of agent substrate, including the triageagent - winner of India National Awards AI Gamechanger 2026.