Remote OpenClaw Blog
What Is ACPX? The OpenClaw Layer for Controlling Codex and Claude via Agents
4 min read ·
ACPX matters because it turns model-specific agent adapters into something you can control through one runtime instead of juggling each backend by hand. That is why the current positioning around ACPX is not just “another CLI.” It is an agent control layer sitting between your operator workflow and specific agent backends like Claude or Codex.
What ACPX Is Actually Solving
the ACPX 0.6.0 release notes frames ACPX as the layer where CLI controls, runtime controls, adapter sessions, and persistent behavior come together. The release notes are full of features that only make sense once you are already controlling agents repeatedly rather than starting from scratch every turn.
That is the key distinction. ACPX is not just about sending a prompt to Claude or Codex. It is about keeping the control surface stable enough that you can treat those agents like reusable runtime components.
Why a Control Layer Matters
Once you use more than one agent backend, the pain shifts fast. The problem is no longer model output alone. The problem becomes session identity, configuration reuse, control commands, persistence, working directories, and adapter-specific weirdness.
That is why ACPX is interesting. The release notes talk about things like system prompt overrides, session pruning, turn handles, persistent session fixes, WSL cwd translation, queue hardening, and clearer error hints. Those are all control-layer problems, not prompt-writing problems.
Where Codex and Claude Fit in the Picture
The 0.6.0 notes explicitly mention forwarding Claude system prompt controls, while also noting Codex and other agents ignore that field where it does not apply. That is exactly what a good control layer should do: expose a consistent surface while still respecting backend-specific behavior.
In other words, ACPX does not make Codex and Claude identical. It gives you a better place to manage the differences.
Stable Session Layer
If the real problem is session control, recovery, and reuse, start with the durable session layer instead of patching the same runtime pain over and over.
Who Should Care About ACPX
If you are still in casual single-turn experimentation, ACPX is probably not the first thing you need. If you are running repeatable coding or operator workflows and the fragility is starting to hurt, then ACPX becomes much more relevant.
The people who benefit most are the ones already feeling the cost of restarts, session drift, and adapter mismatch. ACPX sits exactly where those problems show up.
Primary sources
- the ACPX 0.6.0 release notes, especially the feature list showing system prompt controls, session pruning, turn handles, and persistent session fixes.
- the ACPX repository, which shows ACPX as a public project rather than a one-off release artifact.
- the ACPX README, for the broader runtime context around how ACPX is meant to be used.
Recommended products for this use case
- Session Supervisor — Best fit if your main pain is durable sessions, watchdog checks, and cleaner recovery across long runs.
- Persistent Dev Orchestrator — Best fit if you need background orchestration across multiple agent tasks rather than one stable foreground session.
- Operator Launch Kit — Best fit if you want to build your own control-heavy operator without starting the role design from zero.
Limitations and Tradeoffs
ACPX is still a technical layer. It solves the right problems for repeated agent control, but it does not remove the need to understand your runtime, adapters, and session lifecycle. That is why it is more interesting to serious operators than to casual one-turn users.
Related Guides
- ACPX 0.6.0 Release Highlights
- How ACPX Controls Codex and Claude via Agents
- What Is OpenClaude?
- OpenClaw vs Codex for Long-Running Agent Workflows
FAQ
Is ACPX a model?
No. ACPX is a control layer and runtime surface for agent backends. It sits above specific agents rather than replacing them.
Does ACPX make Codex and Claude behave the same way?
No. The point is not forced sameness. The point is a more stable control surface across different backends.
Who benefits first from ACPX?
People already feeling the pain of multi-turn agent work: session reuse, control commands, persistence, and backend-specific failure modes.