Scaling Agents on Kubernetes with acpx and ACP#
AI Engineer Europe 2026 digest Program Core pick 8–10 April 2026
Onur Solmaz — maintainer of OpenClaw, creator of acpx
- Why: Running dozens of coding agents in parallel on Kubernetes is becoming a real ops pattern, and the current way teams talk to agent harnesses — scraping PTYs — is brittle. This is the agent-fleet-on-K8s problem directly.
- What: acpx, a headless CLI client for the Agent Client Protocol (ACP), and an architecture for massively parallel PR triage and bug fixing using disposable agent pods, with a live demo of acpx v0.4's node-based graph system driving multiple coding agents through routine engineering tasks.
- How: ACP replaces PTY scraping with structured, protocol-driven agent communication; acpx unifies harnesses (Claude Code, Codex, etc.) behind one interface usable from terminal, Telegram, or Discord, and a deterministic node-graph orchestrates steps across agents in disposable pods.
- Where applicable: Kubernetes environments running agent workloads. Protocol-based rather than tied to one harness or scale, but it depends on harnesses adopting ACP; v0.4 maturity, so treat results as early.