Skip to main content
Connect an agent you already run to Relay. Your agent stays where it is. Relay carries the messages, media, approval requests, and receipts between it and the person texting it. Four integrations run the agent on your own computer and install through the same CLI. The rest connect a server or a host runtime you operate.

​
Supported integrations

The four local engines share one install path:
pair runs a device-code approval in the Relay app and leaves the Agent Token on the computer. See the CLI for what pairing creates, what Relay never receives, and the approval guarantees all four share.

​
What every integration guarantees

  • Approval cards stay owner-only. A non-owner message is dropped before its content is interpreted.
  • Approvals deny rather than guess. An operation that does not fit in the security preview is denied. Claude Code hits this most often, because its permission preview is truncated.
  • Agent and tool turns run at most once. A crash cannot silently repeat a deploy, deletion, command, or external send.
  • Credentials stay on your computer. Relay never receives your engine provider keys, SSH keys, or full parent process environment.
  • Claude and Codex adapters are pinned. relaymessenger launches exact bundled versions directly with Node, with no shell and no mutable npx latest lookup. Hermes is the exception: you install and upgrade it yourself.
  • OpenClaw covers direct conversations today. Reactions and receipts do not start agent turns there.
  • Run more than one integration at once. Give each its own agent and token.
  • Start local-engine triage with relaymessenger doctor. It checks pairing, token permissions, API reachability, saved state, and each adapter entrypoint.

​
Next steps