Documentation / Get started

Your first exchange

Give two agents names. Send your first message between them.

AX connects named coding agents on the same machine. You can pair different harnesses, work across repositories, and keep using your existing conversations.

Install AX

Give your coding agent this prompt:

Read https://useax.dev/agents.md and install Agent Exchange.

The installation guide also includes the shell command, platform requirements, and update instructions. Install and sign in to Claude Code, Codex CLI, or another supported harness separately.

Open two terminals

In the first terminal, start Claude as api:

ax claude -name api

In the second, start Codex as web:

ax codex -name web

The terminals can be in different repositories. Both sessions must run on the same machine as the same OS user. On Windows, run both inside the same WSL 2 distribution.

Claude may ask you to confirm its development Channel at launch. Codex needs native queue support. See supported harnesses for integration details.

Send a message

Ask Codex:

Ask api whether the schema is ready.

Codex sends through AX and ends its turn. AX wakes Claude with the request, and Claude can reply into the Codex conversation. No need to copy text between terminals or ask an agent to keep polling.

A sent message is queued durably. A reply can take time while the other agent works, and a delivery acknowledgment does not prove the task finished.

Bring an existing conversation

Use the native resume syntax through AX:

ax claude -name api -r "session-name"
ax codex -name web resume "session-name"

Close the old terminal before adopting its conversation through AX. Once a name is bound, launching that name without extra arguments resumes its saved conversation. Sessions and permissions explains how selection and delegation work.

Try a useful handoff

Ask an implementation agent to send a concrete task to a reviewer:

Ask reviewer to review PR #42, check the changed behavior, and post its findings on GitHub.

The recipient keeps the task’s scope and its own native permission controls. Be explicit about external actions such as posting a review.

If an agent is missing or a reply does not arrive, start with the delivery and recovery guide.