acpx-faq

# acpx FAQ Drive coding agents headlessly through [acpx](https://github.com/openclaw/acpx) (>= 0.19.1). ## Syntax authority Syntax comes from the binary, not this file. `acpx --skill show acpx` is the vendor reference (~39k chars) and the tiebreaker on command shape - do NOT dump it into the transcript. Retrieve in this order: 1. `acpx --help` / `acpx <cmd> --help` - the flags you are about to compose. 2. One topic: `acpx --skill show acpx | rg -B2 -A12 '<term>'`, or a section: `acpx --skill show acpx | sed -n '/^## Sessions/,/^## /p'`. 3. Authoring something novel (a flow, an embedded runtime): dump ONCE to a scratch file and grep that file. This file repeats nothing the reference covers. It carries only what the reference lacks: exit codes, failure semantics, traps, and per-agent recipes. If a syntax question is not answered here, it is answered there - go get it, never guess a flag. The repo's `docs/` (exit-codes, session-control, config) cover some of what the shipped reference omits. ## When this lane acpx is the headless out-of-process executor lane. Inside a herdr pane (`HERDR_ENV=1`) prefer herdr (herdr-faq): it gives you screen reads and dialog detection. Everywhere else (plain terminal, ssh, cron) herdr is untargetable and acpx is the lane. In-session fan-out stays on the harness's own subagent tool. ## Invariants 1. **Global flags precede the agent subcommand** (`--cwd`, `--model`, `--approve-all`, `--agent`, `--format`, `--timeout`, `--ttl`, `--m...