6 ms·
I think there are some primitives for agents that need to be built out for better security and being able to reason about them. Agents run on infra, they have
by alexchantavy 6mo ago
I think there are some primitives for agents that need to be built out for better security and being able to reason about them.
Agents run on infra, they have network connectivity, they have ACLs and permissions that let them read+write+execute on resources, they can interact with other agents.
To manage them from both an infra and security perspective, we can use the existing underlying primitives, but it's also useful to build abstractions around them for management, kind of like how microservices encapsulate compute+storage+network together.
I think of agents as basically microservices that can act in non-deterministic ways, and the potential "blast radius" of their actions is very wide. So you need to be able to map what an agent can do, and it's much easier to do that if there are abstractions or automatic groupings instead of doing this all ourselves.
- verdverm 6mo agoRight, those abstractions and controls already exist in the Kubernetes ecosystem. I can use one set of abstractions for everything, as opposed to having something separate for agents. They are not that different, the tooling I have covers it. There are also CRDs and operators to extend for a more DSL like experience. tl;dr, I don't think the shovel analogy holds up for most of the Ai submissions and products we see here.
- webpolis 6mo ago[dead]
- devonkelley 6mo ago[dead]
- verdverm 6mo agoI'd argue it's both. You also want to know when your agent has collapsed and is burning tokens and your budget.
- takwatanabe 6mo agoAs a psychiatrist, this problem reminds me of something we studied for a long time. Patients get worse in areas we are not measuring, but the numbers we record still look normal. We learned that checking results catches things that checking process cannot catch.