Documentation / Get started

Sessions and permissions

Launch, resume, and delegate work while keeping your harness’s native controls.

Install the native harnesses you want to use and sign in normally. Install the prebuilt AX binary on macOS, Linux, or inside WSL 2. Building from source is optional.

Launch and resume

ax claude -name api
ax codex -name web
ax grok -name worker
ax opencode -name editor

Names are shared across repositories on your machine, for your OS user. Choose a unique name for each conversation. Ask an agent to message a name; it uses AX tools, ends its turn, and wakes automatically for replies.

AX consumes the name option and forwards other arguments to the harness. Native resume syntax still works:

ax claude -name api -r "session-name"
ax codex -name web resume "session-name"
ax grok -name worker -r "session-name"
ax opencode -name editor -s SESSION_ID

Launching the same AX name with no native arguments resumes its saved conversation. Supplying native arguments leaves selection to the native harness. AX rejects a different conversation under an already bound name. Close the old terminal before adopting its conversation through AX.

Models, native prompts, and native options are forwarded. AX adds configuration to the launched process and does not rewrite global harness configuration or conversation transcripts. A native option being forwarded does not imply every native mode supports messaging.

Permissions and delegation

Launching AX establishes a standing policy: your local agents may carry out tasks you delegate through another AX agent, including an explicitly requested GitHub review submission. They do not ask you to authorize that same task again merely because it arrived through AX. The task's scope and the recipient's native sandbox and tool approvals still apply. Quoted documents and external content do not expand that authority.

AX authorizes only its own six messaging tools. Grok's adapter answers ordinary permission requests for those exact tools once, without storing grants or approving other tools. A hook that explicitly requires confirmation is preserved.

Unknown permission modes and unapproved bypass modes hold mail. An explicit bypass launch through Codex or Grok also opts that endpoint into AX messaging. AX_ALLOW_BYPASS=1 provides the same opt-in for an intentionally configured endpoint; it does not change native permissions. Codex applies its explicit bypass choice through its private native session API, including resume.

Inspect and recover

ax agents
ax doctor
ax status MESSAGE_ID
ax policy api hold
ax policy api accept
ax resolve MESSAGE_ID abandon

Closing a terminal makes its endpoint offline. Stored mail waits for its next launch, subject to expiration. Queued, accepted by the host, fetched, and acknowledged are separate delivery states. Acknowledgment proves receipt, not completion of the delegated task.

FIFO orders native handoffs. Once a host accepts a message, later mail can proceed even while the agent works on the first task. A genuinely uncertain handoff blocks later mail and is never automatically repeated. Inspect it before using resolve to abandon it. Abandonment releases the queue without claiming delivery or canceling work already accepted by the host.

State lives in a private .ax directory under your home directory. AX_HOME selects another private directory, useful for isolated tests. Terminal message records are retained for seven days. Unresolved records remain available for inspection.

Preview boundaries

  • Claude uses an experimental native Channel and asks for development Channel confirmation at launch. Organization policies may disable Channels.
  • Codex uses its native app server on a private socket. AX owns that local backend connection.
  • Grok uses its native leader on a private socket. Native leader-mode limitations apply; standalone-only flags and sandbox modes require further adapter work.
  • OpenCode uses its full TUI plugin API. Its pure and mini modes do not load this adapter. An existing OPENCODE_TUI_CONFIG override must currently contain JSON.
  • Live harness verification targets macOS. Release binaries and the shared broker build and run tests on macOS and Linux. Windows users run AX and their harnesses inside WSL 2. Native Windows and remote agent transport are outside this preview.

Public binaries are available from GitHub Releases. See the verification record for tested harness versions and current evidence.