A detailed walkthrough of implementing a multi-agent supervisor pattern on OpenShift using OpenShell sandboxes to enforce least-privilege isolation for AI agents. The pattern addresses the security risks of a single AI agent holding credentials for multiple systems (Prometheus, Loki, Confluence) by splitting work into specialized agents, each running in its own sandbox with kernel-enforced network policies (Landlock, seccomp). The architecture uses Claude as the orchestrating brain in Anthropic's cloud, while actual data access and reasoning happen inside per-agent OpenShell sandboxes on the cluster. Each sandbox gets a scoped network policy allowing only the specific binary to reach specific endpoints, limiting blast radius if any agent is compromised via prompt injection. The post includes a full incident-response demo showing parallel agent dispatch, per-agent policy enforcement, and result synthesis without raw PII ever leaving the cluster.

18m read timeFrom developers.redhat.com
Post cover image
Table of contents
Why isolation matters for agentsWhen a single sandbox is not enoughWhy multiple agents without sandboxes do not helpHow self-hosted sandboxes workA sandbox per sessionOne brain, many sandboxed agentsHow it worksWhat the brain sees versus what it does notPer-agent sandbox isolationThe full flow, from request to resultsTwo agent loops, two trust domainsWhen does the supervisor pattern makes sense?Next steps
67 Impressions