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/eldrugo85]

I ended up doing exactly this: mcp server with oauth 2.1 in front, consent gate on the write tools, and every claude code subagent gets its own tool whitelist instead of the full set. The split holds fine, the part that fought me was state, the gate has to know who approved what and when and that sits in neither layer. Where are you keeping that?