Chat-native control
Start sessions, switch context, send prompts, and cancel work — all from a message thread.
Get started
Open source · Drive any agent
Drive Codex, Claude Code & Gemini sessions from WeChat, Feishu, Yuanbao, Discord — no terminal required.

Works with — runs in
Start it, prompt it, check on it — without ever opening a terminal.
Start a session
One command binds an agent to a workspace.
Send a prompt
Any non-slash message goes straight to the agent.
Stay in control
/status, /cancel, /use — switch live, anytime.
Self-host the relay hub and every instance dials in over WebSocket. Manage all of their sessions — chat, scheduled tasks, orchestration — from one multi-tenant dashboard that renders agent replies as live markdown and works on mobile.
Many instances, one screen
Every box you run dials into the same hub.
Multi-tenant & secure
One access token for web login and connector pairing; tenants see only their own.
Installable PWA
Add it to your home screen; replies stream as markdown.
xacpx bridges a chat message to an acpx agent session running on your machine.
Logical session
xacpx-managed: alias, agent, workspace, per-user chat context.
Transport session
acpx-managed: the real named acpx session on the backend.
A coordinator fans sub-tasks out to workers and gathers results back through the external MCP surface.
Orchestration →Queue prompts with /later — relative or absolute times, in a temporary or a bound session.
Scheduled tasks →WeChat is built in; Feishu and Yuanbao are official plugins — third-party channels follow the same interface, no core changes.
Build a channel →xacpx is a chat-channel console for remotely controlling acpx agent sessions. It acts as a bridge between your chat application and the agent CLI running on your machine, letting you start, switch, and cancel agent work without leaving your phone.
You can use xacpx to drive Codex, Claude Code, Gemini, OpenCode, and any other agent that acpx supports — all from a familiar messaging interface.
xacpx is the right tool when you want lightweight, on-the-go access to long-running agent sessions. Common scenarios include:
If your workflow is entirely local and terminal-based, you do not need xacpx — it adds value specifically through the chat channel layer.
The typical sequence is four steps:
xacpx start/ss codex -d /path/to/project or /use <alias>/ is forwarded to the current session/status, /cancelSession model. xacpx maintains two distinct layers of session state. A logical session is xacpx-managed: it holds an alias, the chosen agent, a workspace binding, and the per-user chat context. A transport session is the actual named acpx session running on the backend. /session new (or the shorthand /ss) creates both at once. /session attach creates only the logical session and binds it to a transport session that already exists — useful when you have an acpx session running independently and want to hook xacpx's chat layer on top of it without disturbing the existing conversation.
xacpx ships with WeChat as the built-in default channel. Additional channels are distributed as official plugin packages:
| Channel | Package | Setup |
|---|---|---|
| WeChat (built-in) | — | Getting Started |
| Feishu | @ganglion/xacpx-channel-feishu | Feishu guide |
| Yuanbao | @ganglion/xacpx-channel-yuanbao | Yuanbao guide |
| Discord | @ganglion/xacpx-channel-discord | Discord guide |
Third-party channels follow the same plugin interface. Install a channel plugin with xacpx plugin add <package>, configure it with xacpx channel add <name>, then restart the daemon.
Chat is not the only way to drive xacpx. Self-host the relay hub — an npm package (@ganglion/xacpx-relay) with a multi-tenant web dashboard bundled in — and manage every instance from a single browser tab. Each instance dials into the hub over WebSocket and registers; the hub never owns your sessions, it just fans them out to your browser.
npm i -g, one port by default, SQLite via the built-in node:sqlite/bun:sqlite, no native addons.xacpx-relay add invite).npm i -g @ganglion/xacpx-relay
xacpx-relay add token # prints the access token once
xacpx-relay start # dashboard + API on :8787See Self-Hosting the Relay Hub for the full walkthrough — pairing, invites, TLS, systemd, and backups.
/ss, /use, /cancel, and more)