skills/acpx/SKILL.md
Use acpx as a headless ACP CLI for agent-to-agent communication, including prompt/exec/sessions workflows, session scoping, queueing, permissions, and output formats.
npx skillsauth add asm3r96/wave-driven-dev acpxInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill when you need to run coding agents through acpx, manage persistent ACP sessions, queue prompts, or consume structured output from scripts.
Use it especially for Wave-Driven Development execution after wave-planner-acpx is approved.
acpx is a headless, scriptable CLI client for ACP (Agent Client Protocol) designed for agent-to-agent automation without PTY scraping.
Core capabilities:
exec)-s/--session)--no-wait)cancel) for in-flight turnsset-mode, set <key> <value>)sessions show, sessions history)status)text, json, quiet)--suppress-reads for cleaner orchestration output--prompt-retries for retrying transient prompt failuressession/set_model--model support for Codex sessionsv0.4.0npm i -g acpx
Prefer global install over npx for stable session reuse.
prompt is default.
acpx [global_options] [prompt_text...]
acpx [global_options] prompt [prompt_options] [prompt_text...]
acpx [global_options] exec [prompt_options] [prompt_text...]
acpx [global_options] cancel [-s <name>]
acpx [global_options] set-mode <mode> [-s <name>]
acpx [global_options] set <key> <value> [-s <name>]
acpx [global_options] status [-s <name>]
acpx [global_options] sessions [list | new [--name <name>] | close [name] | show [name] | history [name] [--limit <count>]]
acpx [global_options] config [show | init]
acpx [global_options] <agent> [prompt_options] [prompt_text...]
acpx [global_options] <agent> exec [prompt_options] [prompt_text...]
Friendly names:
codex -> npx @zed-industries/codex-acpclaude -> npx @zed-industries/claude-agent-acpgemini -> geminiopencode -> npx opencode-aipi -> npx pi-acpqoder -> qodercli --acptrae -> traecli acp serveRules:
codex.--agent <command> is explicit raw command mode.--agent.acpx codex 'inspect failing tests and propose fix plan'
acpx codex 'apply minimal fix and run tests'
acpx exec 'summarize this repo'
acpx codex exec 'review changed files'
acpx sessions new --name backend
acpx codex -s backend 'fix API pagination bug'
acpx codex sessions history backend --limit 20
acpx codex sessions close backend
acpx codex 'run full test suite and investigate failures'
acpx codex --no-wait 'after tests, summarize root causes and next steps'
acpx --format json codex exec 'review changed files' > events.ndjson
acpx codex --prompt-retries 2 'run targeted tests and summarize failures'
acpx --format json --suppress-reads codex exec 'review changed files'
When running worker agents in waves:
-s <agent-name>).Recommended completion marker:
WAVE {WAVE_ID} / {AGENT_NAME} DONE
Recommended worker handoff format:
--agent <command> raw ACP adapter command--cwd <dir> session scope directory--approve-all auto-approve all requests--approve-reads approve reads/searches, prompt for writes--deny-all deny all requests--model <id> request a model when supported by the target agent/session--format <fmt> output: text, json, quiet--suppress-reads hide raw read/search output when cleaner logs are useful--prompt-retries <count> retry transient prompt failures automatically--timeout <seconds> max wait--ttl <seconds> queue owner idle TTL--verbose debug logsPermission flags are mutually exclusive.
Persistent prompt sessions are scoped by:
agentCommandcwdsession nameTips:
--cwd carefully; changing cwd changes session scope.status and sessions show/history to debug state.Parallel named streams:
acpx codex -s backend 'implement contract types for Wave 0'
acpx claude -s docs 'draft migration notes for Wave 0'
Repo-scoped review with permissive mode:
acpx --cwd ~/repos/shop --approve-all codex -s pr-842 \
'review PR #842 for regressions and propose minimal patch'
development
Plan and execute large multi-step, multi-stack changes with contract-first waves, parallel worker ownership, user approval gates, ordered integration, and final verification/docs updates. Use only when the task spans multiple areas (for example frontend, backend, tests, errors, docs) or has dependency-heavy sequencing.
development
Plan and execute large multi-step, multi-stack changes with contract-first waves, parallel worker ownership, user approval gates, ordered integration, and final verification/docs updates using Claude Code Agent subagents. Use only when the task spans multiple areas (for example frontend, backend, tests, errors, docs) or has dependency-heavy sequencing.
tools
Plan and execute large multi-step, multi-stack changes with contract-first waves, parallel worker ownership, user approval gates, ordered integration, and final verification/docs updates through acpx. Use this when you explicitly want cross-CLI or cross-provider workers instead of Codex subagents.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.