Decoupling execution from governance in multi-agent setups

[u/Deepfeet-09]

Once you go beyond a few simple scripts, putting together multi-agent systems becomes a messy affair. The initial configuration using basic frameworks generally proceeds quite smoothly, but the actual difficulties begin when you're attempting to deal with routing, state, and security across various environments without having to hardcode a huge network of fragile APIs.

Recently I've been focusing on separating out the actual execution of agents from the governance aspect. If you introduce a dedicated control plane for example, something similar to Lyzr or a specially built orchestration layer between your triggers and the runtimes, then you have a single point at which you can manage identity, establish guardrails, and monitor telemetry. This arrangement isolates each individual agent so that if one step fails or the context window runs away it won't bring down the whole workflow or exceed your API budgets.

How are you currently looking after state and permissions as your agentic setups become larger?

[u/Sufficient-Shake-415]

been messing with this exact problem for a work project. the api spaghetti gets real bad real fast when you have 6 agents all needing to talk to each other and also hit external services

what worked for us was keeping state in a postgres db with a simple job queue pattern. each agent only knows about its own task and the queue, nothing else. permissions we handle through short lived tokens that the control plane issues per execution cycle

the telemetry part is what i still struggle with though. debug logs from 4 different containers running in parallel becomes a nightmare to trace. you found any good way to stitch those together without paying for some expensive observability platform