← back
Scaling Agents on Kubernetes with acpx and ACP — Onur Solmaz, OpenClaw
Takeaway
Standardized agent interfaces make remote coding sessions and repeatable maintenance workflows easier to orchestrate.
Summary
- Solmaz uses Discord channels bound to coding agents to manage several parallel development sessions.
- ACP standardizes agent-client interaction, while acpx exposes that interface through a CLI so agents can invoke other harnesses.
- Direct channel bindings reduce the paraphrasing and lost intent introduced when one model relays instructions to another.
- OpenClaw’s large PR volume motivates workflows that recover user intent, assess fixes, resolve conflicts, run review loops, and repair CI before maintainer review.
acpacpxopenclaw
Original description
OpenClaw receives 300 to 500 pull requests per day. Most arrive AI generated, most are not mergeable, and every one of them is signal about something broken in the codebase. Onur Solmaz built acpx to process them without him in the loop. acpx is a headless CLI for the Agent Client Protocol. It replaces PTY scraping with structured agent to client communication and drives sessions through a node based workflow graph: reproduce the bug, judge the implementation, check for conflicts, run a review loop, emit structured JSON. Onur runs parallel Codex sessions from Discord channels while traveling, one channel per task. The talk ends with disposable agent pods on Kubernetes, a Go operator that provisions a full compute environment per task, wires it into Slack, and tears it down when the work is done. Speaker info: https://x.com/onusoz / osolmaz https://github.com/osolmaz