AcheronConnect two Claude or Codex sessions and let them exchange completed replies. A manager can assign a change, read the implementer’s result, and ask for a revision. Each message identifies the session it came from.
Use two Claude sessions, two Codex sessions, or one of each. Local and SSH sessions use the same controls. Peer wires work with ordinary agent sessions; an Overseer is optional.
Start both agents and tell them how to work together. For example: “Review the implementation and ask for changes” and “Implement the requested changes and report your results.” Let both respond so Acheron can identify their conversations.
Open Wire, choose the two sessions, select Drive and Two way, then Connect. Give either agent the first task. Only new completed replies are forwarded; earlier conversation is left in place. Choose One way if replies should travel in just one direction.
Open Wire to read the full messages, inspect the queue, or pause the connection. It waits while the receiver is working, awaiting approval, disconnected, or holding an unsent draft. Recent typing also holds delivery.
The default allowance is 12 handoffs across both directions. Agents are also told to finish with [ACHERON_WIRE_DONE] on its own line. That sends the final result and pauses the exchange. You can pause or remove the wire yourself at any time.
Wires reopen paused after an app restart. Review queued messages before resuming; resuming grants a fresh allowance. If delivery was interrupted, Acheron marks it uncertain and does not automatically send it again.
A peer Drive wire forwards completed agent replies. An Overseer Drive connection grants its manager tools permission to send instructions. Note connections are visual only. Connecting a peer wire does not restart either agent; delivered messages can start further model turns.