acpx

You can manage agent-to-agent communication over ACP using a headless CLI client. This approach eliminates PTY scraping by handling structured communication, persistent sessions, and multi-agent workflows directly through the Agent Client Protocol.

Yes, you can run parallel multi-agent workflows within the same repository using named sessions. This feature allows you to maintain multiple distinct workstreams and multi-turn conversations scoped to a single project simultaneously.

To queue prompts for an AI agent while one is running, you can use prompt queuing functionality. This allows you to submit multiple prompts sequentially, which the system will execute in the order they were received.

To maintain multi-turn conversations with coding agents like Claude and Codex, use a CLI client that supports persistent sessions. This keeps conversation context across invocations, enabling efficient code reviews and debugging workflows.

Yes, you can export and import agent session records between machines. The session export and import controls allow you to move session metadata and configurations, facilitating multi-agent workflows across different development environments.

Yes, you need ACP-compatible agents and orchestrators to use this CLI for agent communication. The headless client manages structured interactions over the Agent Client Protocol, requiring compatible endpoints to function properly.